Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhat is the best alternative to Couchbase?
Top Pro
Top Pro
Top Pro
Top Pro
Top Pro
Top Pro
Top Pro
Top Pro
Top Pro
Top Pro
Top Con
Top Con
Top Con
Top Pro
Top Pro
Top Pro
Top Con
Top Pro
Top Pro
Top Pro
Scales very well and useful console to view all their apps and its fully rebrandable which works great if you want to give the clients you are building apps for access to their own view of how it is performing. The fact that it comes with integrated push notifications and their automated monthly report is also great. See More
For companies or large teams of developers, where there are multiple projects being worked on at once, you can choose permissions for any developer and decide who gains access to each app on the backend. Lets you rebrand the system, which works well if you want to give the clients you are building the app for access to their own view of how their app is performing. Also like the fact it comes with the option of integrated push notifications and an automated executive summary report. See More
Setting up a backend for an app with Kinvey is very easy and takes minutes. All you have to do is sign up and through their graphical interface follow all the steps, which boils down to creating tables and identifying the type of data that is being stored. Then you download the library, integrate it with your app and initialize the process with one single line. See More
User registration with Kinvey is pretty good and usually works without any problems. It's also very easy to use, you simply pass the username, password, email, etc. to the required method and register a callback that returns whether the registration was a success or a failure. Same thing is done for login and logout as well. See More
User registration with Parse is pretty good and usually works without any problems. It's also very easy to use, you simply pass the username, password, email, etc. to the required method and register a callback that returns whether the registration was a success or a failure. Same thing is done for login and logout as well. See More
Setting up a backend for an app with Parse is very easy and takes minutes. All you have to do is sign up and through their graphical interface follow all the steps, which boils down to creating tables and identifying the type of data that is being stored. Then you download the library, integrate it with your app and initialize the process with one single line. See More
RethinkDB's ReQL is a very powerful functional query language. The functional aspects of ReQL and the straightforward implementation of the Node driver for Rethinkdb make it a natural fit for Javascript developers. You no longer have to type some obscure syntax in quotes (aka SQL), your queries are just "natural" Javascript functions in the same way you would use lodash to handle your collections. See More
PostgreSQL performance increases with each release, this is also proven by many benchmark tests. Notable performance features include: As PostgreSQL only supports one storage engine, it has been able to integrate and optimise it and with the rest of the database. This has resulted in multiple benefits such as the ability to allow different transaction types to co-exist efficiently without the need to select storage engine types once for each table ahead of time. On the fly data compression resulting in less IO required for reading. Asynchronous + synchronous Replication. PostgreSQL supports a asynchronous API for use by client applications. It is reported to increase performance by up to 40% and is not supported by MySQL. Designed to scale very well with large numbers of cores at high concurrency levels. See More
PostgreSQL is known to have a very holistic approach to robustness and data integrity which is reflected by it being fully ACID compliant. PostgreSQL has always been strict about making sure data is valid before allowing it into the database, and there is no way for a client to bypass those checks. Depending on your requirements, ACID compliance might be important. See More
JSON data can be stored as a column with optional indexes. In 9.4 (upcoming at the time of this writing), JSONB will be a binary version of JSON that will save space. It's like the best of the NO-SQL world without having to give up ACID and Relationships. This means that cascading deletes can be done in a single Transaction across multiple JSON documents. See More
It's a very unfortunate thing, but it's true. Not many people know of this gem so that makes it difficult to find community support at times. It also makes it hard to get people on board with it who shop products by brand name or flashy marketing. It also means there are fewer code snippets, libraries, and frameworks that consider it. While it's interoperability is good with SQL support and Tinkerpop, it still doesn't change the fact that many things don't give it much thought and that can lead to more work as a developer sometimes. See More
A lot of effort went into making OrientDB easy and familiar to use (such as SQL queries for example). However, it's important to understand the database engine a bit and how it works in general (links for example). This involves a bit of a learning curve if you're not familiar with graph databases. Not an enormous curve or anything, but it's still a consideration. See More
Since CouchDB is considered an AP (Available, Partition-Tolerant database management system), it is not really consistent (not all clients can have the same view of the data consistently) and the only way to achieve some "eventual consistency" is through replication and verification of data. See More
MongoDB queries can be very fast because the data is usually all in one place and can easily be retrieved in a single lookup. But this is true only when the data is truly a document. When it's trying to emulate a relational model it starts to become really slow because it may have to perform many independent queries to retrieve a single document. See More
As Node.js uses JavaScript there's no need to map the returned JSON data from MongoDB, as JavaScript is a superset of JSON. Essentially solving object-relational impedance mismatch by its very nature. Working with JSON is also easier overall as it more easily fits into how you would represent data on the client. See More
MongoDB has powerful sharding and scaling capabilities for when the data stored in the database gets so large that a single machine may not be able to store all of it. Sharding solves this problem through horizontal scaling. Mongo gives developers the ability to easily and painlessly add or remove as many machines as needed. See More
Since CouchDB is considered an AP (Available, Partition-Tolerant database management system), it is not really consistent (not all clients can have the same view of the data consistently) and the only way to achieve some "eventual consistency" is through replication and verification of data. See More
The two fatal flaws of many open source solutions is lack of integrated security at the element level and full ACID transaction support. MarkLogic has both and is trusted with some of the worlds most sensitive data. It is the engine that powers healthcare.gov, which despite some early problems (not caused by MarkLogic) is an amazing technological achievement. See More
MarkLogic supports text, documents, key-value/tuple, graphs, tables and object models that don't require extensive data-modeling and normalization that is part of the lifecycle process of relational database management systems. For sites similar to LinkedIn, Facebook, IMDB and even search engines, MarkLogic provides a unique set of features that are all in one box. See More
MarkLogic can store all your enterprise data in it's original format without needing to know a schema in advanced. You can shove pretty much any structured or unstructured data directly into MarkLogic, and it will automatically index everything and make it available for future processing. Of course it is fully schema aware and will apply and enforce schema constraints when available, but the tedious normalization that is required for relational databases is not necessary. See More