A discussion sprung up in a ticket<https://github.com/couchbase/couchbase-lite-java-core/issues/135#issuecomment-41301007> regarding the pros of SQLite vs ForestDB, but the discussion probably doesn't really belong there.
I was hoping to continue the thread here. To recap a bit: *SQLite pros* * Battle tested * Tooling ecosystem * Native libs already integrated into OS *ForestDB pros* * More "natural" fit -- eg, nobody can deny that it's a bit odd to build a NoSQL db on top of a SQL db. * Potentially more compelling concurrency model (Jens -- can you expand on this?) * Potential for parallelized map/reduce indexing (ditto) -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/CACSSHCHjcckreZ1rVh3RZ7vQVBU2WiJiTkk8HwkaWnHzswceuQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
