Tournament of Databases: Road to Resilience

As it’s spring and time for tournaments, we wanted to explore what would happen if the most popular database technologies squared off! This is our (just for fun) view of what might happen if there was a real bake-off based on popularity and functionality. Who would win the hearts and minds of database-lovers around the world?

Round 1 Matchups!

East Region

#1 Oracle vs. #4 InfluxDB - It’s the enterprise incumbent vs. the upstart time series entrant. Will the ever-present, general purpose database win out or will the superpower of a single use case get the underdog  over the victory line?  

#2 MongoDB vs. #3 Elastic - In the battle of scale-outs, it’s the two strongest players in the newer generation of storage systems. They scale out but which can step up to the challenge of winning this battle of scale.

South Region

#1 MySQL vs. #4 AWS DynamoDB - The battle of heavyweights, the most-used open-source database vs. the original cloud-native database. Fully relational semantics vs. scale-out key value store. Who will prevail?

#2 IBM Db2 vs. #3 DuckDB - Will the Cinderella of databases have enough developer momentum to overtake the enterprise player that has been around, for like, forever? Traditional enterprise workloads vs. large scale analytics. Which will win the hearts of fans and carry that momentum to the second round?

West Region

#1 PostgreSQL vs. #4 Neo4J - It’s the trendy open-source database with all the hype vs. the graph database that is having its moment in the age of AI. PostgreSQL has continued to grow in AI with innovation like pgvector but graph workloads have become increasingly important in the age of security and AI. Both come into the tournament riding a wave of excitement.

# 2 Snowflake vs. #3 Cassandra - Will Cassandra “get snowflaked” like some other traditional database powers or will the twisting journey of Cassandra result in a surprising outcome. Sometimes the journey isn’t a straight line.

Midwest Region

#1 SQL Server vs. #4 ClickHouse - The default for Windows developers and Azure aficionados vs. the up-and-coming PostgreSQL-compatible challenger for click stream data (and more). It’s another traditional power vs. an upstart challenger. Will it be another David vs. Goliath or more of a traditional beat down?

#2 Databricks vs. #3 SQLite - This is truly the lightweight (in-process) database vs. the heavyweight, established juggernaut. While Databricks is soaking up lots of database talent in its pre-IPO runup, billions of devices have SQLite running on them every day. Is it a win for the database-for-the-masses or a consolidated powerhouse?

Summary

Results for each round will be posted with commentary and an eventual winner in a few weeks! 

To see what happens, subscribe to the Village Crier or check out VillageSQL on GitHub.