4 ms·
I would only have thought of MySQL.
by I_am_tiberius 6y ago
I would only have thought of MySQL.
- doctor_eval 6y agoMySQL isn't a general solution to problems of scale, because you don't know what problems you're going to have until you have them. So for example if your scaling problem is ACID compliant database updates - say you're the next fintech - then I was under the impression that MySQL would be the last database you'd want to be using. Have I missed something?
- redis_mlc 6y agoThe default MySQL storage engine since 2010 has been Innodb, which is ACID-compliant. Overall, MySQL and Postgres are great Open Source databases, but MySQL has the edge for enterprise features (ie. replication options) and a simpler grant system. Source: DBA.
- I_am_tiberius 6y agoI'm no expert and can't answer that. It was just my impression, and I might be wrong, that for scaling purposes MySQL is better suited. Currently I'm working on a Saas product and the test instance that runs on Digital Ocean sometimes causes connection limit issues (with connection pool) sometimes. Sure my code is maybe not perfectly utilizing connections but I'm really afraid that this happens in production and I don't know how to fix it. On my test environment I just restart everything but on a productive environment I can't do that all the time.
- aidos 6y agoThe default limit on Postgres is 100, so you need to ask yourself why you’re exhausting all those connections. The issue isn’t the dB, it’s the code making the connections. Advice: don’t fret scaling issues, get your fundamentals right