Couchbase Server is a cloud-native, distributed database that fuses the strengths of relational databases such as SQL and ACID transactions with JSON flexibility and scale that defines NoSQL. It is available as a service in commercial clouds and supports hybrid and private cloud deployments.
N/A
Presto
Score 10.0 out of 10
N/A
Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
N/A
Pricing
Couchbase Server
Presto
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Couchbase Server
Presto
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Couchbase Server
Presto
Features
Couchbase Server
Presto
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
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.
Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica
Linking, embedding links and adding images is easy enough.
Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
Organizing & design is fairly simple with click & drag parameters.
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.
Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.
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
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.
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.
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.
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.
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
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
