4 ms·

i'm not suggesting that these departures are the cause of github's issue. rather, i'm saying i don't understand why such a large group from github was hired by

i'm not suggesting that these departures are the cause of github's issue. rather, i'm saying i don't understand why such a large group from github was hired by planetscale if they did not have experience successfully sharding or successfully leveraging vitess this is like if you were building a high-rise condo, would you hire the architects or management company from the building that collapsed in surfside florida? sure, they know what NOT to do next time, but that doesn't mean they do know what TO do

drewbug01 5y ago
I understand what you’re getting at… but why is it you presume that the employees now at planetscale are the reason GH couldn’t shard out their databases? Like, there’s another angle here: management, yeah? Another way of reframing it is “maybe the folks hiring at planetscale know the inside baseball about GH infrastructure”. For example: https://www.linkedin.com/in/isamlambert https://www.linkedin.com/in/isamlambert
- throwusawayus 5y ago
  this is my exact point: they hired the former head of GH infrastructure - literally the person directly responsible for all this at github for years - and made him their ceo github should have sharded years ago, every other large mysql user did so much earlier in their growth trajectory
  - drewbug01 5y ago
    Ah, that’s a more specific point than what you seemed to have been making before.
samlambert 5y ago
Hi, former GitHubber here and CEO of PlanetScale. I came to PlanetScale after seeing the incredible impact that Vitess had at GitHub. The team we have hired here successfully sharded part's of GitHub's very large platform. We continue to shard very large customers at PlanetScale. Platform migrations take a very long time and it's very complicated especially with decade old codesbases. I will say the current team at GitHub are nothing but outstanding people and engineers with a difficult task of managing a very large deployment.

drewbug01 5y ago

I understand what you’re getting at… but why is it you presume that the employees now at planetscale are the reason GH couldn’t shard out their databases? Like, there’s another angle here: management, yeah? Another way of reframing it is “maybe the folks hiring at planetscale know the inside baseball about GH infrastructure”. For example: https://www.linkedin.com/in/isamlambert https://www.linkedin.com/in/isamlambert

throwusawayus 5y ago
this is my exact point: they hired the former head of GH infrastructure - literally the person directly responsible for all this at github for years - and made him their ceo github should have sharded years ago, every other large mysql user did so much earlier in their growth trajectory
- drewbug01 5y ago
  Ah, that’s a more specific point than what you seemed to have been making before.

samlambert 5y ago

Hi, former GitHubber here and CEO of PlanetScale. I came to PlanetScale after seeing the incredible impact that Vitess had at GitHub. The team we have hired here successfully sharded part's of GitHub's very large platform. We continue to shard very large customers at PlanetScale. Platform migrations take a very long time and it's very complicated especially with decade old codesbases. I will say the current team at GitHub are nothing but outstanding people and engineers with a difficult task of managing a very large deployment.