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
MariaDB Platform
Score 9.9 out of 10
N/A
MariaDB is an open-source relational database made by the original developers of MySQL, supported by the MariaDB Foundation and a community of developers. The community states recent additional capabilities as including clustering with Galera Cluster 4, compatibility with Oracle Database, and Temporal Data Tables, allowing one to query the data as it stood at any point in the past.
N/A
Pricing
Couchbase Server
MariaDB Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Couchbase Server
MariaDB Platform
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Couchbase Server
MariaDB Platform
Features
Couchbase Server
MariaDB Platform
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.
Our installation scenario is a MariaDB cluster composed of 3 nodes to achieve high availability in the service and in this way the application that accesses the backend (MariaDB) is always working and is not down at any time.
To achieve high performance of the application when accessing the database, a MariaDB MaxScale has been mounted that acts as a proxy for queries to the database.
MariaDB does well with PHP or Python (django) in a web environment. Developers are able to work quickly.
MariaDB is extremely well documented and has a gigantic support community. If you need ask a question on how to do things you can go to many placces online and find answers quickly.
MariaDB is fast! Queries with tens of thousands of rows are quick.
MariaDB is highly compatible with Oracle's MySQL. Basically the same thing but more open and with a brighter future.
With MariaDB it is so easy to import and export data, and backups are a cinch. This saves me so much time as compared to other RDBMS.
Cluster sizing during the design phase can be improved, especially if the client lacks prior experience. Vendor consultants are very meticulous in order to provide best of class performance and response time, although some more real-world pragmatic approach is often needed.
Couchbase Lite 2 went thru a major revamp, which broke the compatibility of the applications with some features removed and other changed. That needed development teams working to refactor the applications.
Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.
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.
MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.
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.
Yes, I would recommend MariaDB Platform support because they answer very fast and with detailed information. They also help you with the design of the storage infrastructure, not only with the maintenance problems. On the other hand, this service is a bit expensive.
Couchbase could outperform it's competition considerably for database reads and writes. Full text searches were still faster in Elasticsearch but this is more of a feature than a base platform requirement for us.
It did not always compete against these technologies. Most of the time, it was complementing these databases for certain use cases to help provide a much more complete database. This makes more users want to use it to explore new solutions that help users. This is our target and how [we] work with MariaDb.
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
There have been several areas of our application [that] really needed an ACID compliant database (e.g. strong transactional guarantees) that we thought we could work around while using Couchbase. [In my opinion] that turned out to be a poor bet. You need to be certain that the specific characteristics of a NoSQL database fit your problem.
Couchbase does eliminate the need for schema upgrades completely. I.e no downtime or conversion windows as you migrate your data model, adding attributes, etc. This helped with the deployment timeframe associated with DB changes.
The database is (apparently) a bit more of a space/memory consumer than originally anticipated. During deployments, we received constant pressure from Couchbase consulting teams to eliminate/reduce the number of indexes, and this was because any mutations to docs in a bucket must check for impact against all indexes. More recent years have started to address this with their "collections" features, which helps isolate indexes to specific sub-groupings of documents.
MariaDB has saved us enormously on licensing compared to our previous DB software vendor.
In service, it has enabled us (speaking as the internal DB team here) to provide better service to the other teams in the company as well as our customers, with less staff.
The level of hardware required for adequate performance, in our environment, has been much lower. Those savings have been substantial, above and beyond savings on licensing and DBA staffing levels.
