3 ms·
I’ve been thinking lately that maybe the most reasonable path would be using SQL early on so you have a very clear picture of your schema, and you can do migrat
by atom_arranger 6y ago
I’ve been thinking lately that maybe the most reasonable path would be using SQL early on so you have a very clear picture of your schema, and you can do migrations easily.
Once you scale up and your schema and access patterns have solidified then you can make the switch to NoSQL where it makes sense.
- mercer 6y agoI suppose it depends on the specific project or feature. Usually I go for the approach you describe. But more than once I got bitten by doing this for a feature or project where things were still very much in flux, and/or in a prototyping phase. In those cases, starting with 'NoSQL' (JSONB columns in Postgres though) would've saved me a lot of trouble, and it would have been much easier, relatively speaking, to migrate my data into proper tables once things solidified. Still, I do find that going for 'SQL' by default has usually been the better choice.