databases

Finally, no JavaScript. But it is now getting exciting for software manufacturers who have long earned a lot of money with database licenses. Where will this money go if open source databases are so popular? Maybe to operations, say the magic cloud? The days of processor-core-based licenses are almost over , but even so there will probably be a DB2 installation running on some AIX machine in a bunker in 2142. We only listed databases that were mentioned by at least five developers.

An interesting additional mention is "C-Tree", a database that was not on our screen at all. Microsoft Access was named twice, funnily enough for "I like it" and not for "Replace it". Whether the addition of "Big JSON Files" was given as a joke, or is effectively used, we leave open.

-->Relevant data online as Excel

Databases developers use

• Clear Frontrunner here is MySQL. This placement is not only supported by PHP developers. Even with Java developers, MySQL leads with 132 mentions before MSSQL with 132. A big surprise is that C# developers use almost as much MySQL (181) as MSSQL (185). But as we will see later, MySQL is quite a controversial solution.
• Important: MariaDB in position six is a so-called fork of MySQL, It was created after Oracle bought MySQL. Since both solutions are compatible one could argue that its users should be added up. This would mean that MySQL and MariaDB together would have nearly twice as many users as the next database on the list.
• In addition to SQL and NoSQL databases, there are also specific areas such as Neo4j a graph database or Redis and Memcached as super fast key-value stores.

MySQL	350
Microsoft SQL Server	261
PostgreSQL	231
Oracle	199
SQLite	188
MariaDB	163
MongoDB	139
Elasticsearch	139
Redis	97
Firebase	50
Google Cloud Storage	47
IBM Db2	30
Memcached	28
Amazon RDS/Aurora	26
Microsoft Azure Cosmos DB	21
Neo4j	19
Amazon DynamoDB	17
Cassandra	17
Couchbase	17
C-Tree*	11
Google BigQuery	10
H2*	9
Apache HBase	9
DynamoDB	9
Apache Hive	6
Amazon Redshift	5

If you separate the list by SQL and NoSQL, it looks like this on the SQL side:

MySQL & MariaDB    513
Microsoft SQL Server    261
PostgreSQL        231
Oracle            199
SQLite            188
IBM Db2        30
Amazon RDS/Aurora    26
Cassandra        17
Google BigQuery    10
H2*            9
Apache Hive        6

The NoSQL page follows below. Of course, it is debatable what falls under which category. For example, Elasticsearch is mainly used for search solutions, but can also be used as a normal NoSQL database. NoSQL already has a large following with MongoDB in first place. Nevertheless, SQL-based relational databases are clearly ahead.

MongoDB        139
Elasticsearch        139
Firebase        50
Microsoft Azure Cosmos DB    21
Amazon DynamoDB    17
Couchbase        17
C-Tree*            11
DynamoDB        9
Apache Hive        6

Databases developers would like to use

At first glance, it becomes clear that the preferences go in the direction of NoSQL - especially MongoDB. Also eliciting some excitement are Elasticsearch for full-text searches and Neo4j for Graph databases. There is Firebase a NoSQL database, which can directly serve as a backend with an API for apps and single page applications.

PostgreSQL ranks third in SQL databases. But again, MySQL and MariaDB are in front of the classic SQL databases.

MongoDB	82
Elasticsearch	74
PostgreSQL	73
Neo4j	45
Firebase	40
Redis	38
Google Cloud Storage	34
MySQL	29
Cassandra	29
MariaDB	24
SQLite	23
Microsoft Azure Cosmos DB	22
Couchbase	22
Microsoft SQL Server	19
Amazon DynamoDB	18
Google BigQuery	15
Memcached	12
Apache Hive	12
Oracle	10
Amazon RDS/Aurora	9
Apache HBase	9
Amazon Redshift	6

Databases developers like

MariaDB and MySQL are back on top, almost twice as strong as the others. Followed by PostgreSQL as a powerful open source solution. Exciting is SQLite, a solution that is mainly used directly embedded in applications, without having to operate a separate service.

MySQL	204
PostgreSQL	189
SQLite	128
Microsoft SQL Server	123
MongoDB	115
MariaDB	111
Elasticsearch	98
Redis	86
Oracle	71
Firebase	44
Neo4j	33
Google Cloud Storage	23
Memcached	22
Amazon RDS/Aurora	22
Microsoft Azure Cosmos DB	18
Cassandra	17
Amazon DynamoDB	17
Couchbase	14
IBM Db2	10
Google BigQuery	9
Apache HBase	7
DynamoDB	6

Databases developers don't like

Again it is important to compare how many actually use a solution that do not like it. For example Oracle, where out of 199 users, 103 do not like the solution. If you sum up the voices for MySQL and MariaDB, it's almost as many as MSSQL, but with the first-mentioned duo used much more. PostgreSQL stands out because of the many developers who use it, only a few say they do not like it.

Oracle	103
Microsoft SQL Server	92
MySQL	68
IBM Db2	31
MongoDB	22
SQLite	20
MariaDB	17
Elasticsearch	17
Microsoft Azure Cosmos DB	14
PostgreSQL	13
Google Cloud Storage	12
Redis	10
Memcached	10
Cassandra	10
Amazon DynamoDB	10
Firebase	9
Amazon RDS/Aurora	9
Google BigQuery	9
Couchbase	8
Teradata	8
Amazon Redshift	7
Neo4j	6
Apache HBase	6
DynamoDB	6
Apache Hive	6

Databases developers want to adopt

Here we see the result from the last question confirmed: Anyone who wants to introduce a new SQL database, clearly favors open source with PostgreSQL, MongoDB, MariaDB, ElasitcSearch etc. This is followed by the usual suspects in all areas. It should be noted, however, that only very few developers would like to introduce MSSQL or Oracle in relation to their distribution.

PostgreSQL	64
MongoDB	39
MariaDB	32
Elasticsearch	32
Redis	28
MySQL	22
SQLite	22
Microsoft SQL Server	16
Oracle	9
Google Cloud Storage	8
Firebase	8
Neo4j	6
Cassandra	5
Microsoft Azure Cosmos DB	4
Amazon DynamoDB	4
Amazon RDS/Aurora	4
IBM Db2	3

Databases developers want to replace

• Here, too, the findings related to SQL are confirmed: Those who want to replace MySQL like to use MariaDB. This database was created after the sale of MySQL to Oracle. A sale that has caused a lot of displeasure. With MySQL and Oracle, two products from the same company are at the top of the "get rid of" list.
• We should also point out that some participants want to replace MongoDB or Firebase again, although it is likely to be one of the more recently introduced solutions.

MySQL	66
Oracle	61
Microsoft SQL Server	55
IBM Db2	20
MongoDB	19
SQLite	13
PostgreSQL	8
MariaDB	8
Elasticsearch	6
Google Cloud Storage	6
Firebase	6
Redis	4
Microsoft Azure Cosmos DB	4
Memcached	4
Couchbase	4
Cassandra	3
Amazon RDS/Aurora	3
Apache HBase	3
Teradata	3

Databases developers want to keep

• Again a confirmation for the combo MySQL and MariaDB - but also for PostgreSQL, MSSQL, SQLite and MongoDB.
• But we also want to point out that almost as many developers want to keep Oracle as there are developers who want to replace it.

MySQL	130
PostgreSQL	115
Microsoft SQL Server	98
SQLite	78
MongoDB	60
MariaDB	59
Elasticsearch	59
Oracle	49
Redis	44
Firebase	20
Memcached	15
Google Cloud Storage	13
Amazon RDS/Aurora	9
Neo4j	9
Couchbase	8
Cassandra	8
Amazon DynamoDB	6
Google BigQuery	5