[renewiltord]

Kube is great. Abstracts away lots of problems. If you make a single kube cluster (which is trivial with eksctl) you can iterate on a number of startup ideas pretty quickly on it.

The kube API (the pod/deployment/service/ingress structure) is where the magic is, imho. Sure you could just make an EC2 instance, and swap in your Rails, and redirect the ALB and fix your domain CNAME, but whatever man, you can do like 4 of those things in an instant in Kube.

[stickfigure]

You know what abstracts away all those problems but doesn't require hours a day of mucking with scripts? Google App Engine. Heroku. Elastic Beanstalk.

[jordanthoms]

Good at smaller scale, and Heroku can go pretty good at scale. But eventually you run into things that they make harder rather than easier if you need to do something which doesn't fit well with their model. Deploying onto Google Kubernetes Engine has a bit of boilerplate setup work, but after that it's not a huge management overhead considering everything it gives you.

[renewiltord]

Okay, yeah, for sure. I think they're better options for early iteration. I guess actions speak louder than words here since my preferred operational stack is Rails + Typescript + React + Redux + Heroku w/ Heroku Postgres.

Yeah, definitely Heroku over k8s for idea validation.

I think there's definitely room in the k8s-based space for slightly past that, though.

[hn-hipsters]

Outdated stuff.

I use the Jojoma framework to abstract away all that Kube stuff. It's trivial to use through Baobab, especially if you use the Wazabi framework-as-a-service framework (which you should). All you have is to deploy the proclets through a DMVC and it's all automagic.

I iterate through 17 startup ideas a day using that setup.

[renewiltord]

I genuinely thought for a second you were describing something new that I'd missed the boat on. Hahaha!

[antonvs]

Still using the JBWD stack huh.