3 ms·

That's an interesting story re: early twitter. Are you certain a MySQL SLA-level support contract would have solved their scalability issues? My understanding i

That's an interesting story re: early twitter. Are you certain a MySQL SLA-level support contract would have solved their scalability issues? My understanding is that it was high volume of highly followed participants that led to congestion. I.e. a design problem. Eventually solved by caching and fanning out replicated tweet data to all followers. To see the issues around cloud and open source right now, you only have to look at who's winning: enterprise consultants such as Dell EMC, HPe, Accenture, IBM, etc. They are the ones pushing broad K8S adoption at the edge. And in the next generation it will probably come down to a new crop of ISVs to solve issues around data portability, vendor lock-in, security, pricing arbitrage, and training.

scarface74 7y ago
You think any of those are “winning” compared to AWS or MS with Azure? Everyone you mentioned is lumped together as “other” in most pie charts. Despite all of the wide eyed idealists architects, at a certain scale you are always locked into your infrastructure choices. No your CTO is not going to migrate from your six figure Oracle installation because you use the repository pattern to abstract your database access. There are far too many risks and too many chances for regressions with little pay off to migrate from a working infrastructure.
evanweaver 7y ago
> Are you certain a MySQL SLA-level support contract would have solved their scalability issues? This pitch may have been mentioned in passing to me but I don't remember. From the perspective of I and many others who ultimately solved the scalability issues, the MySQL boat was simultaneously sinking and on fire, while nobody knew who the captain was supposed to be. An insurance policy that promised that somebody with a badge would dedicate 8 hours a month to buffing out scratches was not useful. It was less "it's OSS, we don't need to pay" and more "only God can help us now".

scarface74 7y ago

You think any of those are “winning” compared to AWS or MS with Azure? Everyone you mentioned is lumped together as “other” in most pie charts. Despite all of the wide eyed idealists architects, at a certain scale you are always locked into your infrastructure choices. No your CTO is not going to migrate from your six figure Oracle installation because you use the repository pattern to abstract your database access. There are far too many risks and too many chances for regressions with little pay off to migrate from a working infrastructure.

evanweaver 7y ago

> Are you certain a MySQL SLA-level support contract would have solved their scalability issues? This pitch may have been mentioned in passing to me but I don't remember. From the perspective of I and many others who ultimately solved the scalability issues, the MySQL boat was simultaneously sinking and on fire, while nobody knew who the captain was supposed to be. An insurance policy that promised that somebody with a badge would dedicate 8 hours a month to buffing out scratches was not useful. It was less "it's OSS, we don't need to pay" and more "only God can help us now".