Couchbase vs Apache Derby

• Key/value data store. Couchbase is blazing fast at data access and retrieval when you know what keys you want to access.
• Data querying with N1QL. If you have your indexes set up right, searching your unstructured data can be really fast too.
• Management dashboard. The Couchbase platform has a great admin panel that provides tons of insights into how your cluster is performing.

Read full review

• Much easier to use and learn than most commercial databases.
• Derby database errors are well documented.
• Most complex queries supported as well as by other database vendors.

Read full review

• Should allow servers to change their roles on the fly - currently you will need to take down the server and re-assign roles
• SDK documentation is not as helpful and should have more examples
• No pre-compiled procedures - unlike in SQL Server, Couchbase does not have pre-compiled stored procedures therefore we have to run various test to optimize our application

Read full review

• Not as well positioned in the market as the "big dogs" (Oracle, MSSQL)
• Been around awhile, and not a lot of exposure. This I believe is primarily due to it's relation to the Apache Project (which is not bad, but they don't force big, lumbering corporate volume licensing on you), and thus people are a bit gun-shy about NOT throwing money at something
• Java is still "slow" compared to C/C++, thus making Derby a bit slow too

Read full review

• We can implement the mobile app using community release.
• The peer to peer syncing technology saves our development time.
• The CRUD process will be stopped when index and view are growing rapidly, we have to delete index files and reindex again.

Read full review

• Saved money on database licensing.

Read full review