3 ms·
Start with SQL and only move to NoSQL when necessary. Users > 10.000.000+: Moving some functionality to other types of DBs (NoSQL, graph, etc) Inte
by frik 11y ago
Start with SQL and only move to NoSQL when necessary.
Users > 10.000.000+:
Moving some functionality to other types of DBs (NoSQL,
graph, etc)
Interesting insights from Amazon. While not everyone will agree, there is apparently some truth in it.
- collyw 11y agoThe isn't usually a good reason to start with a NoSQL solution, except for buzzwords on your CV.
- UK-AL 11y agoOr the fact there data sets that fit nosql databases seem to work far better. Patient records is one I can think off.
- billmalarky 11y agoThese data sets can be easily handled by Postgresql's JSONB data type.
- collyw 11y agoOr a normal table.
- deleted 11y ago[deleted]
- UK-AL 11y agoCan but its not the best. This is obvious since most patient record systems these days do not use SQL. They use things like MUMPS.
- billmalarky 11y agoNormal tables don't elegantly handle certain types of data. I'm not saying you can't make it work, but there's a valid reason why people choose to use document stores over traditional tables in certain cases.