If CouchDB is MySQL, then TouchDB is SQLite.
By “CouchDB-compatible” I mean that it can replicate with CouchDB and Couchbase Server, and that its data model and high-level design are “Couch-like” enough to make it familiar to CouchDB/Couchbase developers. Its API will not be identical and it may not support some CouchDB features (like user accounts) that aren’t useful in mobile apps. Its implementation is not based on CouchDB’s (it’s not even written in Erlang.) It does support replication to and from CouchDB.
In my books a perfect solution must:
- be small
- be fast
- reuse the target platform technologies (so it feels at home)
- support bi-directional synchronization with CouchDB
- provide an API that is either similar to the target platform APIs or is similar to CouchDB API
Original title and link: TouchDB: Embeddable Lightweight CouchDB-compatible ( ©myNoSQL)