Atomicity requires that each transaction be "all or nothing"
Consistency property ensures that any transaction will bring the database from one valid state to another.
Isolation property ensures that the concurrent execution of transactions results in a system state that would be obtained if transactions were executed sequentially
Durability property ensures that once a transaction has been committed, it will remain so, even in the event of power loss, crashes, or errors.
Why use SQlite?
Embedded SQL Database Engine
Serverless – accesses disk directly
faster than popular database engines
Single file
Cross Platform / Architecture
Small footprint
Zero configuration
Portable
Who uses SQlite?
Adobe Lightroom, AIR
Airbus flight software
Apple Mail, Safari
Google Chrome, Android
Macafee Antivirus
Mozilla Firefox
Microsoft Windows 10, Skype
Flame maleware
SQlite Datatypes
NULL
Integer
Real
Text
BLOB
SQlite Limitations
It is said you can’t use SQLite in production because it doesn’t support concurrency (no more than one user can be writing to the database at the same time) and it can’t scale.But many applications are used only by a few users.
For example, they are used on an intranet of a small company. Or maybe they have some hundreds of read only users, but only ten or twenty users who can write to the database.