to the 
Slant community chat on DiscoursePro High performance
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...
Pro Support for JSON data type
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...
Pro Fully ACID compliant
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 check...
Con Not suited for small apps
Because of it's complexity and power, it may be an overkill to use PostgreSQL in small applications that will not make use of it's full power.
Pro Horizontal scalability
RethinkDB is scalable horizontally. It has support for sharding, parallel queries and MVCC concurrency.
Pro Changefeeds (change listeners)
You can listen to changes and trigger code based on these changes.
Con No user accounts
This is just the database, you need to setup your own auth and user accounts (such as using Auth0).
Pro Simple Map/Reduce support
The M/R system lets you process terabytes of documents in parallel, save the results, and only need to reprocess documents that have changed on subsequent updates. While not as powerful as Hadoop, it is an easy to use query system that's hard to screw up.
Pro Replicate and sync with the browser via PouchDB
You can keep a synced copy of your database on the client-side with PouchDB. This allows for much faster data access than HTTP would allow, and offline usage.
Con Can only achieve consistency through replication and verification
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 da...
Pro Flexible
Serverless, limitless and easy to implement and use.
Con Limited locking
Locking is done at file/database level -- effectively only one process or thread can update at a time. This puts a severe limit on the scalabilty of this database for server applications.
Pro Easy to scale
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...
Pro Doesn't require a unified data structure
Mongo is very flexible in that it doesn't require a unified data structure across all objects. So it's rather easy to use.
Con Reported to loose or corrupt data
MongoDB is famously known for leaking and losing data over time.
Con Document Stores may be not suited for relational data
MongoDB has no JOIN, all relations are supposed to be resolved client-size which entails additional requests to the server.
Pro Supports joins
Unlike many NoSQL databases, ArangoDB does support joins in AQL queries.
Know any negative aspects of this option?
Pro Lots of community support available
As MySQL is used by a lot of people, there's a good number of libraries, tutorials and examples available that should help you through all kinds of situations.
Pro Scalable
MySQL is made to handle a lot of data and to be used in large applications. This makes it extremely scalable and fast, even under a lot of workload.
Con Error messages usually are not very detailed
When you are trying to do something in MySQL and something goes wrong it will simply give you an error message with an error code. WHich does not say much about what went wrong unless you look it up online. This can be a little cumbersome during development.
Pro Ability to make predefined fast queries
With Couchbase you can make "Views" of data, which are practically predefined queries which are fetched with an O(1) algorithm.
Pro Open source
Couchbase and Couchbase Mobile are open source and released under the Apache License.
Con No way to manage data through a CLI
Data hosted on Couchbase can only be managed through the Couchbase GUI. There's no way to do it through the terminal.
Pro Effortless/Automatic Scaling
Orchestrate was built for scale. Orchestrate is a full-fledged distributed data system, provided as a multi-tenant service. There is no need to manage finite server resources like disk space, CPU, or memory
Pro Already set up for you
Orchestrate is a Database-as-a-Service, so there is no downloading, installation, or any other administration. It also makes configuration management and deployment easy.
Con Data are not on your server
Since it's a DBaaS, your data are completely on their server. It cannot be run on your server. Backup is handled by them as well, which may be good or not depending on your needs.
Con Not Open Source
Orchestrate is not an open source solution.
Comments
Welcome to the Slant Community
Stop spending hours researching
Slant is written by a community helping you be informed. Let us know what you’re passionate about to get an awesome personalized feed.