Couchbase vs MarkLogic Server

• 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

• Search was really advanced. Hard to set up and had limitations about semantical meanings between xml nodes, but provided very good search abilities.
• The organization of documents across collections and metadata was particularly useful.
• The REST abilities were very advanced and worked with XQuery well.

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

• MarkLogic still has a long way to go in fostering the developer community. Many developers are gravitating to the simple integrations and do not delve into the deeper capabilities. They have made tremendous strides in recent months and I am sure this will improve over time.
• Many of the best features are left on the floor by enterprises who end up implementing MarkLogic as a data store. MarkLogic needs to help customers find ways to better leverage their investment and be more creative in how they use the product.
• Licensing costs become a major hurdle for adoption. The pricing model has improved for basic implementations, but the costs seem very prohibitive for some verticals and for some of the most advanced features.

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

• MarkLogic reduced the amount of time that the DevOps team needed to dedicate to database updates, as the engineering team was mostly able to easily design and maintain database upgrades without requiring specialists such as database architects on the DevOps side. This capability flowed from the product's speed and the versatility of its XQuery language and libraries.
• MarkLogic required significant education and buy-in time for the engineering team.

Read full review