Best for
Cache, session, rate limit, queue-like state, counters, and short-lived fast access.Good as a speed layer next to PostgreSQL or MySQL, not as the only database.Teams choose it when the cache workload is a real product need.
Back to choosercache database
Redis
Cache, session, rate limit, queue-like state, counters, and short-lived fast access.
Common use cases
- Cache, session, rate limit, queue-like state, counters, and short-lived fast access.
- Good as a speed layer next to PostgreSQL or MySQL, not as the only database.
- Teams choose it when the cache workload is a real product need.
When not to use it
You need the primary durable source of truth for orders, money, or compliance records.
Common pairings
PostgreSQLMySQL
Use it when the workload clearly matches; keep the first version operationally simple.
Keep learning before you build.
This page is educational first. Use the project workflow only when you are ready to turn the choice into evidence and a report.