3 ms·
Yep. We just started implementing it at my place. I had only just started and wanted to say that it seemed like overkill, but it was under way when I started an
by collyw 7y ago
Yep. We just started implementing it at my place. I had only just started and wanted to say that it seemed like overkill, but it was under way when I started and bringing that up in my first week didn't seem like a good way to start.
Top be fair it has reduced our server costs a bit (after maybe 6 months of developer time). I am unconvinced it will be worth the hassle.
- aaronbrethorst 7y agoFTE dev, fully loaded, is what? $250,000 per year? More? Are the improvements worth $125,000?
- collyw 7y agoWe are in Spain, no San Francisco, so a fair bit lower than that. IF the startup goes well and we need to scale maybe it will be worth it. And it does give us the advantages of high availability. Though one comment I saw about Kubernetes on here a few weeks back concerned an old schooler like me. The guy suggested that if something goes wrong, just kill the pod and let kubernetes bring up another. Apparently that's the way you are supposed to do things. Something seems really wrong with that approach to me. Just throw resources at the problem with very little understanding of why things went wrong.
- cutler 7y agoDocker + Kubernetes = the death of YAGNI