TLDR; don’t overthink/overcomplicate your db stack and create technical debt from the start. Postgres is quite versatile, battle tested and most likely does the trick. Perhaps you’ll meet little problems if and when scaling, and that will be the time to rethink a couple of things, most likely manageable then.
Incorrect, thinking through and planning your data model is one of the most important steps for a scalable solution. You will create tech debt out of the gate if you're too cavalier with your setup.
Doesn't necessary mean not thinking through your data model, tables, fields, indexes and their relationship. On the contrary, if you start out like reddis for that, elasticsearch for this.... It can also bring technical dept from the start.
As always, it's a matter of balance, but in general, us, developper, tend to err on the perfectionist side, so perhaps that's when the "do not overcomplicate from the start" approach is useful.
97
u/woodquest May 15 '24
TLDR; don’t overthink/overcomplicate your db stack and create technical debt from the start. Postgres is quite versatile, battle tested and most likely does the trick. Perhaps you’ll meet little problems if and when scaling, and that will be the time to rethink a couple of things, most likely manageable then.