5 ms·

if not k8, what would other people be using? ECS?

k8sToGo 3y ago
From my experience, classical VMs with self written Bash scripts. The horror!
kenhwang 3y ago
If you're on AWS, yeah, I'd say just use ECS until you need more complexity. Our ECS deployments have been unproblematic for years now. Our K8s clusters never goes more than a couple days without some sort of strange issue popping up. Arguably it could be because my company outsourced maintenance of it to an army of idiots. But K8s is a tool that is only as good as the operator, and competence can be hard to come by at some companies.
- p_l 3y ago
  K8s or no K8s, outsource to lowest bidder and you'll get unworkable platform :|
  - kenhwang 3y ago
    Agreed. But if you're already on AWS, I'd say the quality floor is already higher than the potential at 95%+ of other companies. So I say unless you're at a company that pays top salaries for the top 5% of engineering talent, you're probably better off just using the AWS provided service.
    - p_l 3y ago
      I used to have a saying back when Heroku was more favourable, is that you use Heroku because you want to go bankrupt. AWS is at times similar. Depending on your local market, AWS bills might be way worse than the cost of few bright ops people who will let you choose from offerings including running dev envs on random assortment of dedicated servers and local e-waste escapees
liveoneggs 3y ago
ECS is so nice and simple. http://kubernetestheeasyway.com http://kubernetestheeasyway.com
nprateem 3y ago
Cloud run, etc, but there seem to be some biggish gaps in what those tools can do (probably because if deploying a container was too easy the cloud providers would lose loads of profit).
evantbyrne 3y ago
I honestly think docker compose is the best default option for single-machine orchestration. The catch is that you either need to do some scripting to get fully automated zero downtime deploys. I have to imagine someone will eventually figure out a way to trivialize that, if they haven't already. Or, you could just do the poor man's zero downtime deploy: run two containers, deploy container a, wait for it to be ready, then deploy container b, and let the reverse proxy do the rest.
- KronisLV 3y ago
  Docker Swarm takes the Compose format and takes it to multi-node clusters with load balancing, while keeping things pretty simple and manageable, especially with something like Porainer! For larger scale orchestratiom, Hashicorp Nomad can also be a notable contender, while in some ways still being simpler than Kubernetes. And even when it comes to Kubernetes, distros like K3s and tools like Portainer or Rancher can keep managing the cluster easy.
- ancieque 3y ago
  If you want to stick on one machine, you can always just use a single node Docker Swarm to get the fully automated zero downtime deploys you want with Docker Compose: https://github.com/BretFisher/ama/discussions/146 https://github.com/BretFisher/ama/discussions/146

From my experience, classical VMs with self written Bash scripts. The horror!

If you're on AWS, yeah, I'd say just use ECS until you need more complexity. Our ECS deployments have been unproblematic for years now. Our K8s clusters never goes more than a couple days without some sort of strange issue popping up. Arguably it could be because my company outsourced maintenance of it to an army of idiots. But K8s is a tool that is only as good as the operator, and competence can be hard to come by at some companies.

p_l 3y ago
K8s or no K8s, outsource to lowest bidder and you'll get unworkable platform :|
- kenhwang 3y ago
  Agreed. But if you're already on AWS, I'd say the quality floor is already higher than the potential at 95%+ of other companies. So I say unless you're at a company that pays top salaries for the top 5% of engineering talent, you're probably better off just using the AWS provided service.
  - p_l 3y ago
    I used to have a saying back when Heroku was more favourable, is that you use Heroku because you want to go bankrupt. AWS is at times similar. Depending on your local market, AWS bills might be way worse than the cost of few bright ops people who will let you choose from offerings including running dev envs on random assortment of dedicated servers and local e-waste escapees

liveoneggs 3y ago

ECS is so nice and simple. http://kubernetestheeasyway.com http://kubernetestheeasyway.com

nprateem 3y ago

Cloud run, etc, but there seem to be some biggish gaps in what those tools can do (probably because if deploying a container was too easy the cloud providers would lose loads of profit).

evantbyrne 3y ago

I honestly think docker compose is the best default option for single-machine orchestration. The catch is that you either need to do some scripting to get fully automated zero downtime deploys. I have to imagine someone will eventually figure out a way to trivialize that, if they haven't already. Or, you could just do the poor man's zero downtime deploy: run two containers, deploy container a, wait for it to be ready, then deploy container b, and let the reverse proxy do the rest.

KronisLV 3y ago
Docker Swarm takes the Compose format and takes it to multi-node clusters with load balancing, while keeping things pretty simple and manageable, especially with something like Porainer! For larger scale orchestratiom, Hashicorp Nomad can also be a notable contender, while in some ways still being simpler than Kubernetes. And even when it comes to Kubernetes, distros like K3s and tools like Portainer or Rancher can keep managing the cluster easy.
ancieque 3y ago
If you want to stick on one machine, you can always just use a single node Docker Swarm to get the fully automated zero downtime deploys you want with Docker Compose: https://github.com/BretFisher/ama/discussions/146 https://github.com/BretFisher/ama/discussions/146