Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityThe Best 1 of 16 OptionWhy?
Top Pro
•••Top Pro
•••Top Pro
•••
Top Pro
•••
Top Pro
•••
Top Pro
•••
Top Pro
•••
Top Pro
•••
Top Pro
•••
Top Pro
•••
Top Con
•••Top Pro
•••Top Con
•••
Top Con
•••
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
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
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
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
An SQLite database is a single ordinary disk file that can be located anywhere in the directory hierarchy. It works by sending requests to a single file where all the data is kept instead of communicating with a hosted database which gives access to an interface by making use of sockets and ports. The file format used is also cross-platform, so can easily be migrated to various machines. This makes SQLite extremely portable throughout different applications, all that's needed to transfer the whole database is to make a copy of the file. See More
Because of it's ability to scale and with the portability that a single-file database gives you without losing much of the power and features that SQL gives developers, it's a great choice for testing applications and for the early stages of development when the workload and the data that needs to be stored is not that large. See More
SQLite has bindings for a large number of programming languages, including BASIC, Delphi, C, C#, C++, Clipper//Harbour, Common Lisp, Curl, D, Free Pascal, Haskell, Java, JavaScript, Livecode, Lua, newLisp, Objective-C (on OS X and iOS), OCaml, Perl, PHP, Pike, PureBasic, Python, R, REALbasic, REBOL, Ruby, Scheme, Smalltalk, Tcl, Visual Basic. 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
Because of it's popularity there are a lot of tutorials and guides out there that help developers install and work with MySQL. The installation process itself is not very hard and there are multiple powerful GUI tools that make it extremely easy to work with MySQL for a beginner. 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
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