3 ms·
No-SQL databases have their pros and cons and so do SQL databases. Would it be feasible to use both, from within the same application, depending on the type of
by galaxyLogic 4y ago
No-SQL databases have their pros and cons and so do SQL databases.
Would it be feasible to use both, from within the same application, depending on the type of data in question?
The SQL vs. No-SQL debate has been going on for along time. Why not use both? Has anybody tried that?
- kumarvvr 4y agoFor small apps, which are most apps, a distributed, managed, partitioned postgresql cluster is sufficient. Heck, even a single one on a good machine is sufficient. It has a colorful mix of SQL and NoSQL constructs, interacted on SQL queries.
- tehlike 4y agoFor small apps, go with SQLite.
- RedShift1 4y agoYou don't need to switch to MongoDB to have a JSON document server. Postgres has excellent JSON support, you can just put it all in Postgres. Bonus feature: you can easily migrate your unstructured data to structured data.
- Tostino 4y agoAnd another bonus, yay your backups are now all consistent and you can focus on one technology stack instead of two. Reducing the cognitive load is important in large code bases.
- redwood 4y agoI've never understood the conflating of JSON-like with "unstructured": I would call this richly structured