Different databases get designed for different scenarios. Using one database technology for every situation doesn’t make sense, and can lead to non-optimal solutions for common issues. Big data and IoT applications, high availability, secure backups, security, cloud vs. on-premises deployment: each have a set of requirements that might need a special technology. Relational, document-based, key-value, graphical, column family – there are many options for many problems. More and more, database environments combine more than one solution to address the various needs of an enterprise or application (known as polyglot persistence).
Please take a few seconds and answer the following poll on database technologies. Which are you using? Help the community learn what technologies critical database environments employ. Please select from one to six technologies as they apply to your environment.
If you’re using other solutions or have specific issues, feel free to comment below. We’ll post a follow-up blog with the results!
Which of the following open source database technologies do you use?
- MySQL (MariaDB, Percona Server, etc.) (36%, 1,412 Votes)
- Redis (12%, 486 Votes)
- MongoDB (11%, 444 Votes)
- PostgreSQL (11%, 432 Votes)
- ElasticSearch (9%, 356 Votes)
- Memcache (8%, 308 Votes)
- Cassandra (4%, 141 Votes)
- Spark/Hadoop (3%, 118 Votes)
- Kafka (3%, 109 Votes)
- CouchBase (1%, 41 Votes)
- Neo4j (1%, 39 Votes)
- Riak (0%, 12 Votes)
Total Voters: 1,619