3 ms·

So 1/4 to 3/4 of a million per year in salary. Plus disrupting all the developers. So far every large scale implementation i have seen has cost the developers

So 1/4 to 3/4 of a million per year in salary. Plus disrupting all the developers. So far every large scale implementation i have seen has cost the developers a year in productivity.

brianwawok 6y ago
Hi. I run my production 7 figure ARR SaaS platform on google hosted k8s. I spend under 10 minutes a week on kubernetes. Basically give it an hour every few months. Otherwise it is just a super awesome super stable way for me to run a bunch of bin-packed docker images. I think it’s saved me tons of time and money over lambda or ECS. It’s not F500 scale, but it’s over 100 CPU scale. Confident I have a ton of room to scale this.
- kasey_junk 6y ago
  Tbf you are an experienced operation savvy engineer. Your hourly is astronomically high so you’ve minimized your costs via experience.
  - brianwawok 6y ago
    Hey you worked with me and know I am neither experience nor savvy :)
- gravypod 6y ago
  If you end up making a blog post about how you do your deployments/monitoring and what it's enabled you to do I think it'd be a great contrast to the "kubernetes is complicated" sentiment on HN.
  - brianwawok 6y ago
    This sounds like fun. Kind of a “how to use Kubernetes simply without drowning”. Though would it just get downvoted for not following the hacker news meme train?
gravypod 6y ago
I have heard of people taking "years" to migrate to kube but only on HN and only on company who's timelines for "lets paint the walls of our buildings" stretch into the decades. But, even once you move, you get benefits that other systems don't have. 1. Off the shelf software (even from major vendors [0]) 2. Hireable skill set: You can now find engineers who have used kubernetes. You can't find people who've already used your custom shell scripts. 3. Best practices for free: zero-downtime deploys can now be a real thing for you. 4. Build controllers/operators for your business concepts: rather than manually manage things make your software declaratively configured. [0] - https://cloud.netapp.com/blog/cvo-blg-kubernetes-storage-an-in-depth-look#H_H1_4 https://cloud.netapp.com/blog/cvo-blg-kubernetes-storage-an-...

So 1/4 to 3/4 of a million per year in salary. Plus disrupting all the developers. So far every large scale implementation i have seen has cost the developers a year in productivity.

brianwawok 6y ago

Hi. I run my production 7 figure ARR SaaS platform on google hosted k8s. I spend under 10 minutes a week on kubernetes. Basically give it an hour every few months. Otherwise it is just a super awesome super stable way for me to run a bunch of bin-packed docker images. I think it’s saved me tons of time and money over lambda or ECS. It’s not F500 scale, but it’s over 100 CPU scale. Confident I have a ton of room to scale this.

kasey_junk 6y ago
Tbf you are an experienced operation savvy engineer. Your hourly is astronomically high so you’ve minimized your costs via experience.
- brianwawok 6y ago
  Hey you worked with me and know I am neither experience nor savvy :)
gravypod 6y ago
If you end up making a blog post about how you do your deployments/monitoring and what it's enabled you to do I think it'd be a great contrast to the "kubernetes is complicated" sentiment on HN.
- brianwawok 6y ago
  This sounds like fun. Kind of a “how to use Kubernetes simply without drowning”. Though would it just get downvoted for not following the hacker news meme train?

gravypod 6y ago

I have heard of people taking "years" to migrate to kube but only on HN and only on company who's timelines for "lets paint the walls of our buildings" stretch into the decades. But, even once you move, you get benefits that other systems don't have. 1. Off the shelf software (even from major vendors [0]) 2. Hireable skill set: You can now find engineers who have used kubernetes. You can't find people who've already used your custom shell scripts. 3. Best practices for free: zero-downtime deploys can now be a real thing for you. 4. Build controllers/operators for your business concepts: rather than manually manage things make your software declaratively configured. [0] - https://cloud.netapp.com/blog/cvo-blg-kubernetes-storage-an-in-depth-look#H_H1_4 https://cloud.netapp.com/blog/cvo-blg-kubernetes-storage-an-...