3 ms·
Lesson 1.1: Occasionally, ignore lesson 1. I once worked on a game (Pokemon GO) that went from zero users to over 100 million users in a bit over two weeks. S
by alasdair_ 7y ago
Lesson 1.1: Occasionally, ignore lesson 1.
I once worked on a game (Pokemon GO) that went from zero users to over 100 million users in a bit over two weeks.
Scaling was still very, very stressful but it wouldn't have happened at all without Kubernetes.
Thanks guys.
- rawoke083600 7y agoThat's Why I said "probably" and not "always", on how many projects have you worked before and after pokemon go that went from zero to 100mil users ?
- rumanator 7y agoIt's better to accept a tad more complexity upfront than having to figure out midflight how to scale an unscalable solution. Perhaps another good example is how voat failed to capitalize on reddit's mass exodus because mostly their service was rendered unusable by their apparent inability to scale.
- mburst 7y agoI think Kubernetes adds quite a bit of complexity if you've never worked with it before. As does any technology though really. Much easier these days to drag sliders right for more server resources if needed from AWS, GCP, Heroku, etc. Sure it'll cost more, but you have 100mil users and if your system doesn't scale horizontally you probably have a problem that isn't going to be solved by Kubernetes or any other orchestration system. As an aside I think Voat failed because the community that came was toxic and the team behind it had no intentions of quelling it. https://gizmodo.com/goodbye-and-good-riddance-to-voat-reddits-gross-clone-1795337099 https://gizmodo.com/goodbye-and-good-riddance-to-voat-reddit...
- alasdair_ 7y agoHonestly? I now work at Facebook and the answer to that question is “all of them”