CouchDB vs Titan

• It can replicate and sync with web browsers via PouchDB. This lets you keep a synced copy of your database on the client-side, which offers much faster data access than continuous HTTP requests would allow, and enables offline usage.
• Simple Map/Reduce support. The M/R system lets you process terabytes of documents in parallel, save the results, and only need to reprocess documents that have changed on subsequent updates. While not as powerful as Hadoop, it is an easy to use query system that's hard to screw up.
• Sharding and Clustering support. As of CouchDB 2.0, it supports clustering and sharding of documents between instances without needing a load balancer to determine where requests should go.
• Master to Master replication lets you clone, continuously backup, and listen for changes through the replication protocol, even over unreliable WAN links.

Read full review

• Titan is really good for abstraction of underlying infrastructure. You can choose between different storage engine of your choice.
• Open source, backed by community, and free.
• Supports tinkerpop stack which is backed by apache.
• Uses gremlin for query language making the whole query structure standardized and open for extension if another graph database comes along in future.

Read full review

• NoSQL DB can become a challenge for seasoned RDBMS users.
• The map-reduce paradigm can be very demanding for first-time users.
• JSON format documents with Key-Value pairs are somewhat verbose and consume more storage.

Read full review

• The community is lacking deep documentation. I had to spend many nights trying to figure many things on my own. As graph databases will grow popular, I am sure this will be improved.
• Not enough community support. Even in SO you might not find many questions. Though there are some users in SO who quickly answer graph database questions. Need more support.
• Would love an official docker image.

Read full review

• It has saved us hours and hours of coding.
• It is has taught us a new way to look at things.
• It has taught us patience as the first few weeks with CouchDB were not pleasant. It was not easy to pick up like MongoDB.

Read full review

• Steep learning curve. Your engineers would have to spend lots of time learning different components before they feel comfortable.
• Have to plan ahead. Maybe this is the nature of graph databases, but I found it difficult to change my schemas after I had data in production.
• It is free, so time is the only resource you have to put in titan.

Read full review