3 ms·
I'm really curious why MySQL was dropped instead of being optimised? SQL databases can (and do) scale to high volumes, and would have avoided a lot of re-engin
by marcus_holmes 7y ago
I'm really curious why MySQL was dropped instead of being optimised?
SQL databases can (and do) scale to high volumes, and would have avoided a lot of re-engineering. What was the final blocker for WePay that meant that optimising SQL could go no further?
- Thaxll 7y agoThey don't really scale since MySQL / PG don't have built in features for horizontal scaling / sharding ect ... If you want to make it scale you have to do a lot of things manually / use third party tools / solutions.
- marcinzm 7y agoSQL on it's own scales to a point, that point being however large you can make a single machine. Which can be quiet small depending on the data sizes in question. Beyond that you need to use something like Vitess (which the article mentions) but that comes with it's own overheads and caveats. You no longer have SQL really, you have Vitess. A couple years ago a company I was at tried to use Vitess but found too many edge cases and too much operational overhead.