Electronic Books

Suitable for sites with around 200 to 300 concurrently browsing visitors.
Incredibly fast access times when accessed locally (that is, by using a scripting language on a
local SQLite file), even so far as to be faster than most enterprise - level systems.
Easier to back up. No need to normalize the database before backups are made, plus the
database need only be downloaded to fully back up.
All data inserts, deletes, and updates are transactional, plus any system failure, including a
complete crash, will safely roll back a transaction.
And, here are the cons:
Very slight latency if accessed remotely.
Dirty pages (uncommitted data) can take around 256KB for every 1MB of stored data.
Not really suitable for websites exceeding a couple of gigabytes in data.
As the database is a file, all read and write locks exist database wide rather than object wide,
meaning too many simultaneous visitors (300+ on average) slow down the user experience.
Conclusion
As noted above, the SQLite database is suitable for 95 percent of websites.


Pages:
517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541