3 ms·
Over the years I’ve learned two things when it comes to picking a database when starting a new project 1 - most data is inherently relational 2 - Postgres is
by SOLAR_FIELDS 3y ago
Over the years I’ve learned two things when it comes to picking a database when starting a new project
1 - most data is inherently relational
2 - Postgres is pretty good at basically any problem you throw at it, pretty scalably. It will fall over at bonkers amount of scale in some cases but you probably won’t have bonkers amount of scale
Thus, if you want to pick any new data store that isn’t Postgres for your project, the default is Postgres. You have to specifically convince me that Postgres is not good enough for this specific use case if you want me on board for anything else as a data store.
- zachmu 3y agoIt's a pretty good default stance, yeah. We have been trying to convince people to use our new database [1] for several years and it's an uphill battle, because Postgres really is the best choice for most people. They really have to need our unique feature (version control) to even consider it over Postgres, and I don't blame them. [1] https://github.com/dolthub/dolt https://github.com/dolthub/dolt