New ask Hacker News story: Ask HN: Is MySQL 8, in 2022, a safe DB for storing financial data?
Ask HN: Is MySQL 8, in 2022, a safe DB for storing financial data?
2 by profwalkstr | 0 comments on Hacker News.
I've joined a financial startup which is in the process of building a MVP and they want to use MySQL instead of PostgreSQL as the main DB (their critical DB, the DB which will store all financial transaction data). Think checking accounts, transactions, ledgers, credit cards, investment, etc. All of this will be stored in MySQL with InnoDB. My main concern is data loss and corruption. I know that HN and Reddit hates MySQL and praises PostgreSQL, but their arguments make sense to me: - Team more familiar with MySQL. It's better to use something that you know the defects and workarounds than to use something that's better in theory but you don't know how to tame it. - MySQL has more documentation and training resources. There are excellent, up to date O'Reilly books about it from the development, optimization and administration perspectives. Just from O’Reilly there is: Learning SQL [focused on MySQL], Learning MySQL [not to be confused with the former], High Performance MySQL, Efficient MySQL Performance, MySQL Cookbook. And all of them are up to date. The official docs are also very good. On the PostgreSQL side, no such resources, there seems to be no recent good books about it - the O'Reilly book is about a very old version and the Packt ones don't count, Packt books are usually sh t. Also, the official docs seem meh (example: the MONEY type should not be used, but you wouldn't know this from the manual [https://ift.tt/vOTI1jf], there's not even any mention on it being bad; you'd know it's bad only if you had read https://ift.tt/nbSMI1i - Most complaints online seem to be about MySQL 5, which is very old and which problems mostly been fixed in modern versions, or about installations running without SQL strict mode on. - PostgreSQL is also not immune to problems: https://ift.tt/q1mRCjF However, I experienced, multiple times, data loss and corruption with MySQL and MariaDB, as recently as 2017. That makes me uneasy to fully trust it. What do you think, from a perspective of data integrity and reliability, about storing mission critical financial data in modern* MySQL? Can it be trusted? Anecdotes about ancient versions will not be useful. Is anyone here running it for this kind of workload? Is PostgreSQL still considered safer than MySQL in 2022 or has MySQL caught up in that department? The main worry is not about features or speed, the main worry is data loss and corruption.
2 by profwalkstr | 0 comments on Hacker News.
I've joined a financial startup which is in the process of building a MVP and they want to use MySQL instead of PostgreSQL as the main DB (their critical DB, the DB which will store all financial transaction data). Think checking accounts, transactions, ledgers, credit cards, investment, etc. All of this will be stored in MySQL with InnoDB. My main concern is data loss and corruption. I know that HN and Reddit hates MySQL and praises PostgreSQL, but their arguments make sense to me: - Team more familiar with MySQL. It's better to use something that you know the defects and workarounds than to use something that's better in theory but you don't know how to tame it. - MySQL has more documentation and training resources. There are excellent, up to date O'Reilly books about it from the development, optimization and administration perspectives. Just from O’Reilly there is: Learning SQL [focused on MySQL], Learning MySQL [not to be confused with the former], High Performance MySQL, Efficient MySQL Performance, MySQL Cookbook. And all of them are up to date. The official docs are also very good. On the PostgreSQL side, no such resources, there seems to be no recent good books about it - the O'Reilly book is about a very old version and the Packt ones don't count, Packt books are usually sh t. Also, the official docs seem meh (example: the MONEY type should not be used, but you wouldn't know this from the manual [https://ift.tt/vOTI1jf], there's not even any mention on it being bad; you'd know it's bad only if you had read https://ift.tt/nbSMI1i - Most complaints online seem to be about MySQL 5, which is very old and which problems mostly been fixed in modern versions, or about installations running without SQL strict mode on. - PostgreSQL is also not immune to problems: https://ift.tt/q1mRCjF However, I experienced, multiple times, data loss and corruption with MySQL and MariaDB, as recently as 2017. That makes me uneasy to fully trust it. What do you think, from a perspective of data integrity and reliability, about storing mission critical financial data in modern* MySQL? Can it be trusted? Anecdotes about ancient versions will not be useful. Is anyone here running it for this kind of workload? Is PostgreSQL still considered safer than MySQL in 2022 or has MySQL caught up in that department? The main worry is not about features or speed, the main worry is data loss and corruption.
Comments
Post a Comment