Likelihood to Recommend if you're doing joins from hBASE, hdfs, cassandra and redis, then this works. Using it as a be all end all does not suit it. This is not your straight forward magic software that works for all scenarios. One needs to determine the use case to see if Apache Drill fits the needs. 3/4 of the time, usually it does.
Read full review Best suited when edge devices have interrupted internet connection. And Couchbase provides reliable data transfer. If used for attachment Couchbase has a very poor offering. A hard limit of 20 MB is not okay. They have the best conflict resolution but not so great query language on Couchbase lite.
Read full review Pros queries multiple data sources with ease. supports sql, so non technical users who know sql, can run query sets 3rd party tools, like tableau, zoom data and looker were able to connect with no issues Read full review Couchbase performance is exceptional both for in-memory and persisted transactions. Handling of node failures and cluster rebalancing (high availability). Enterprise support from Couchbase themselves Good documentation Streaming of bucket (database) level mutations via their Database Change Protocol (DCP). Replication of datasets between native clients and Couchbase buckets Handling of simultaneous writes to the same record with performance penalties Read full review Cons deployment. Not as easy configuration isn't as straight forward, especially with the documentation Garbage collection could be improved upon Read full review The N1QL engine performs poorly compared to SQL engines due to the number of interactions needed, so if your use case involves the need for a lot of SQL-like query activity as opposed to the direct fetch of data in the form of a key/value map you may want to consider a RDBMS that has support for json data types so that you can more easily mix the use of relational and non-relational approaches to data access. You have to be careful when using multiple capabilities (e.g. transactions with Sync Gateway) as you will typically run into problems where one technology may not operate correctly in combination with another. There are quality problems with some newly released features, so be careful with being an early adopter unless you really need the capability. We somewhat desperately adopted the use of transactions, but went through multiple bughunt cycles with Couchbase working the kinks out. Read full review Likelihood to Renew if Presto comes up with more support (ie hbase, s3), then its strongly possible that we'll move from apache drill to prestoDB. However, Apache drill needs more configuration ease, especially when it comes to garbage collection tuning. If apache drill could support also sparkSQL and
Flume , then it does change drill into being something more valuable than prestoDB
Read full review I rarely actually use Couchbase Server, I just stay up-to-date with the features that it provides. However, when the need arises for a NoSQL datastore, then I will strongly consider it as an option
Read full review Usability Couchbase has been quite a usable for our implementation. We had similar experience with our previous "trial" implementation, however it was short lived.
Couchbase has so far exceeded expectation. Our implementation team is more confident than ever before.
When we are Live for more than 6 months, I'm hoping to enhance this rating.
Read full review Performance One of Couchbase’s greatest assets is its performance with large datasets. Properly set up with well-sized clusters, it is also highly reliable and scalable. User management could be better though, and security often feels like an afterthought. Couchbase has improved tremendously since we started using it, so I am sure that these issues will be ironed out.
Read full review Support Rating I haven't had many opportunities to request support, I will look forward to better the rating. We have technical development and integration team who reach out directly to TAM at Couchbase.
Read full review Alternatives Considered compared to presto, has more support than prestodb. Impala has limitations to what drill can support apache phoenix only supports for hbase. no support for cassandra. Apache drill was chosen, because of the multiple data stores that it supports htat the other 3 do not support. Presto does not support hbase as of yet. Impala does not support query to cassandra
Read full review The
Apache Cassandra was one type of product used in our company for a couple of use-cases. The Aerospike is something we [analyzed] not so long time ago as an interesting alternative, due to its performance characteristics. The
Oracle Coherence was and is still being used for [the] distributed caching use-case, but it will be replaced eventually by Couchbase. Though each of these products [has] its own strengths and weaknesses, we prefer sticking to Couchbase because of [the] experience we have with this product and because it is cost-effective for our organization.
Read full review Scalability So far, the way that we mange and upgrade our clusters has be very smooth. It works like a dream when we use it in concert with AWS and their EC2 machines. Having access to powerful instances along side the Couchbase interface is amazing and allows us to do rebalances or maintenance without a worry
Read full review Return on Investment Configuration has taken some serious time out. Garbage collection tuning. is a constant hassle. time and effort applied to it, vs dedicating resources elsewhere. w/ sql support, reduces the need of devs to generate the resultset for analysts, when they can run queries themselves (if they know sql). Read full review Great performance. Leading Couchbase Lite capabilities for mobile use. Developers' learning curve with replica reads and multi cluster can be long. Needs guidance and nurturing. Cluster maintenance during OS patching, etc. has multiple ways to approach. Operational teams may need some guidance. Read full review ScreenShots