Database Decision Helper
Not sure whether to reach for PostgreSQL, MongoDB, Redis, or DynamoDB? Answer a few questions about your application below and this tool suggests which one (or combination) fits, and why. It's a starting point for your own evaluation, not an authoritative decision.
Data shape
How is your information typically organized?
Relationships
Do different pieces of your data need to be connected or cross-referenced (e.g. a customer is linked to their orders and payments)?
Consistency
If two related actions need to happen together, do both need to succeed or fail as a single unit, with no in-between state?
Query patterns
How will people typically look up or ask questions of your data?
Workload
Will your system mostly be read from a lot, or written to a lot?
Scale
How much do you expect usage or data volume to grow over time?
Schema flexibility
How often do you expect the shape of your information to change (e.g. new details being added over time)?
Data expiration
Does some of your information naturally expire or become irrelevant after a while?
Caching
Do you need a fast, temporary helper for frequently accessed information (e.g. login sessions, popular pages), separate from your main storage?
PostgreSQL
No signal points here yet — toggle a filter to see this update.
MongoDB
No signal points here yet — toggle a filter to see this update.
Redis
No signal points here yet — toggle a filter to see this update.
DynamoDB
No signal points here yet — toggle a filter to see this update.
Toggle a filter above to start building your recommendation.