Table of contents Show Hide
The choice between SQL and NoSQL depends on your data structure and how you query it, not on hype.
SQL for transactions and relations
If you need referential integrity, complex transactions and reports, a relational engine like PostgreSQL is hard to beat.
NoSQL for scale and flexibility
Documents and key-value shine in catalogs, sessions and bulk loads where the schema changes fast.
Think hybrid
Many systems use a relational database as the source of truth and a NoSQL store for read scaling.