Reviews (1-25 of 40)
Less suited in scenarios where lots of pre-existing relational data access models already exist in the application stack and need to be replaced in order for Couchbase to be implemented.
- It helps developers to develop an application that is responsive.
- It is flexible, to provide continuous delivery.
- It provides consistent performance.
- It is easy to deploy and use the software.
- It has a high learning curve.
- Data manipulation languages sometimes may fail to work.
- It performs the role of a key value store very well.
- It can be used as a system of engagement when architected properly.
- Provides reliable performance with scalability and adequate security.
- More practical/flexible licensing terms when used in a container environment.
- Comprehending logs and taking action at times is a very difficult activity.
- I wish Couchbase could be used as a system of record, I would be excited to see this happen.
- Couchbase is easy to set up in the cloud or on the on-premise servers. Within minutes you can get yourself a database that will cheap, conveniently accessed, and highly available. More than that - it'll retain the way to query it like a traditional RDMS.
- Couchbase is easy to maintain because high availability is one of its main features. You can build your Couchbase cluster on, say, 10 virtual boxes in the cloud, and have all the work on the database side done without any interruption to your applications.
- Couchbase has great customer support. They are always ready to help when you face a problem. Tickets opened easily and get a quick response on support.couchbase.com. Documentation is awesome.
- N1QL query language (very close to a standard SQL) is great when your application cannot rely entirely on key-value gets. This makes it easy to convert the tables of legacy RDMS and applications accessing it to the new generation of apps-database combo.
- General recommendation from Couchbase would be to have RAM on servers big enough to fit 20-25% of a dataset. This is promised to be driven down to just single percents with release 6.5 in summer of 2019. This can drive the cost of underlying servers dramatically for huge TB databases.
- Indexes are tied to specific servers. It'll be nice at some point to have them spread across all index nodes and be able to rebalance indexes the same way as data itself.
It is being used for all layers of our website, and by several other support systems, again mainly as a fast caching system across multiple servers in a cluster.
- Fast fetching of data
- Easy to implement N1QL queries
- Even faster queries when using indexes
- Easier method to increase the number of nodes in a cluster
- Official support for Node.JS sessions
- The ability to see when a document will expire
- Easy user interface.
- Bi-directional replication is good.
- Fails tolerance.
- Index of documents.
- A migration tool from other SGBDs to Couchbase.
- Rest API commands 100% compatible with MongoDB for migrations applications without change code.
- Certification's program.
Mobile integration is more or less.
- Full-Text Search.
- Simple syntax.
- Shallow learning path.
- New features in supposedly stable releases commonly have major issues.
- The engineers Couchbase send out to help us use their products could be more technical.
- The Couchbase whitepaper is far from intuitive as to what is going on under the hood.
- Reliability: rarely goes down.
- Supporting legacy DB applications: Putting Couch in front of slow running applications seems to be a good fit.
- SDK: Documentation could be better. Questionable decision making in terms of how things work.
- Speed: It's being used for our caching solution, however, nobody probably should do this. Far better platforms that handle caching better.
- Community: Can be frustrating trying to solve problems seems the community and gender issues vary depending on the version.
- Tuning/troubleshooting tools: Improvement should happen in this area.
- Adoption: Small compared to other noSQL solutions.
Couchbase makes business easy and simple. Since Couchbase uses NoSQL, it's very flexible and versatile to create and maintain documents where our clients require change over time. It`s extremely handy to modify the documents on the go. With no specific schema, we can work with different types of data with varying lengths. Seeking and accessing data takes less time compared to traditional RDBMS.
But Couchbase does introduce a few problems. Since schema is absent, there are no validations on the data. Triggering data inserts/updates needs to be handled separately. Short procedures have now become lengthy java classes. Unnesting and accessing elements of the array takes forever, and it usually fails with a timeout.
Considering the pros and cons, moving to Couchbase is a good decision for mobile and web developers, and for new companies.
- Schema-free. Today's changing demands in mobile and web development is well suited with the free document structure that Couchbase offers.
- Snappy results. Couchbase is faster than traditional RDBMS.
- Couchbase supports ACID “transactions” on a per-document level.
- Could benefit from triggers during transactions, so that the other documents get updated automatically, or to execute a particular logic.
- Schema type validation on individual fields, whilst providing a schema-free document structure, would be great.
Couchbase is not preferred to be implemented for legacy applications that are only needing maintenance.
- Easy sync protocol to mobile devices, the minimal code needed to pull data down to a device.
- Powerful indexing that can be as simple or as complex as you need, allowing for quick lookups for commonly used data sets.
- Great analytics present in the server dashboard that allows you a great top-down view of system usage, resources, etc.
- Bit of a steep learning curve to get a cluster set up, especially with sync gateway.
- Performs well.
- Support should be highly available immediately as these are used for mission-critical systems.
- Support for auto backup restore schedule within the console.
- Increase the limit of the number of buckets.
- Easy to use.
- Easy to administrate after setting it up.
- Simple database use case
- 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.
- The Couchbase mobile suite is great, in theory. In practice we have found the sync to be somewhat unreliable, to the point where we had to write our own logic to push data to the server. We have not had a chance to upgrade to the new 2.0 version of mobile yet, so these issues may have been resolved there.
- 5 years later, the sync gateway component still isn't integrated into the main data platform. The Couchbase platform does a really great job at letting you independently scale services, but the sync gateway is still a standalone component. I get the feeling there is a rift between the Couchbase mobile team and Couchbase server team, or possibly that the Couchbase mobile product is just a side project or second-class citizen in the Couchbase world.
- One of the reasons that initially drew us to Couchbase was their touted dedication to open source development. Over the past year or so, they have really backed off on that. At the 2018 Couchbase connect conference, I didn't even hear the phrase 'open source' mentioned once. If you really dig into the source code that is available, you'll find that pretty much all new features are being developed closed-source in private repositories. So while you can build the 'community edition' yourself, it's not even close to what the full platform offers. So if you do hear any mention of 'Couchbase is open source', be aware that it's a bit of a facade.
If you want to store tons of data records with varying schemas or totally unstructured data, Couchbase is also a great fit. Their N1QL engine is pretty amazing and pretty fast, but don't expect SQL level performance.
If you're building a simple application with traditional relational data and on a tight budget, I'd say stick with something like Postgres.
However, if you need schema validation or enforcement, it lags behind, because that's not the point of the database. Also, because N1QL relies heavily on indexes, I wouldn't recommend it if you plan to do a lot of ad-hoc queries on your production data, as enabling the general index on a production server is not recommended.
It may not be suitable for source of records like member account information that needs to be kept for audit purpose.
Couchbase Scorecard Summary
Feature Scorecard Summary
Couchbase is a multi-model NoSQL database for mission-critical applications. It is designed to help deliver ever-richer and ever more personalized customer and employee experiences. Built with powerful NoSQL technology, the Couchbase Data Platform was architected on top of an open source foundation for the massively interactive enterprise. The geo-distributed Engagement Database promises to provide developer agility and manageability, as well as performance at any scale.
Customers include industry leaders Amadeus, AT&T, BD (Becton, Dickinson and Company), Carrefour, Cisco, Comcast, Disney, DreamWorks Animation, eBay, Marriott, Neiman Marcus, Tesco, Tommy Hilfiger, United, Verizon, Wells Fargo, as well as hundreds of other household names. For more information, visit www.couchbase.com.
Couchbase Technical Details
|Operating Systems:||Windows, Linux, Mac|