WhatDbShouldIUse

About

About WhatDbShouldIUse.

A practical database recommendation resource for developers, architects, and teams choosing modern data systems.

How to choose the right database

Choosing the right database is not about picking the most popular option—it is about matching your database to your workload. The right choice depends on factors like workload type (OLTP vs OLAP), query complexity, schema evolution, latency requirements, and operational constraints.

Instead of relying on generic comparisons, modern systems require evaluating trade-offs across scalability, consistency, and performance.

What this project does

WhatDbShouldIUse is a guided database selection tool that helps developers and teams compare SQL, NoSQL, vector databases, streaming systems, and analytical warehouses.

It narrows down database choices based on real-world constraints and provides a practical shortlist tailored to your use case.

Who this is for

This tool is designed for developers, backend engineers, architects, startups, and AI teams building modern applications.

Whether you are choosing a database for an MVP, scaling a production system, or designing AI-powered applications, the goal is to simplify decision-making.

What databases are covered

The tool covers relational databases, NoSQL systems, vector databases for semantic search, streaming platforms, time-series databases, and analytical warehouses.

It supports modern use cases including real-time systems, AI retrieval (RAG), analytics, and large-scale distributed applications.

How the selection works

The guided picker evaluates your requirements across workload shape, consistency guarantees, query patterns, scaling strategy, and operational overhead.

👉 Learn how the decision model works

Why use a database selection tool

Choosing the wrong database can lead to scaling issues, performance bottlenecks, and costly migrations. A structured approach helps avoid these problems early.

This tool focuses on real-world trade-offs instead of generic feature lists.

The project

WhatDbShouldIUse is built to help teams make better database decisions using practical constraints instead of assumptions.

Maintainer

WhatDbShouldIUse is created by Akshith Varma Chittiveli, an engineer focused on building scalable systems and simplifying complex architecture decisions.

For updates and insights, connect on LinkedIn.