7 ms·
I have found myself enjoying using a document database as the online store, and then using a 'big data solution' (we use Presto) for any analytics queries later
by __float 6y ago
I have found myself enjoying using a document database as the online store, and then using a 'big data solution' (we use Presto) for any analytics queries later.
Traditional migrations for relational databases are really painful. Document databases make this much easier, and if you've faced the operational pain of needing to migrate a large database (for example, it's so easy to accidentally lock an entire table in Postgres), you might be pretty compelled.
(That said, I think the pendulum is swinging back away from document databases. So you're in luck ;))
- thehappypm 6y agoI think the parent is arguing that it's hard to do useful big-data analysis on highly nested structures of data. When your database is storing some immense JSON blob, it's hard to write SQL against it.
- mohaine 6y agoHow do you normalize your Json structure so it can be queried? Do you enforce a schema on your JSON or do you morph it on export into a common structure. If you enforce a schema on the Json structure how do you handle the changes on the live system?