Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker Releases Plugin for Simplified Deployments into AWS

infoq.com

Post reply on HN
Print view View original

21–30 of 116 posts

Re: Docker Releases Plugin for Simplified Deployments into AWS

#21

Post by mplewis »

chopraaa wrote: post #18
miked85 wrote: post #10

I guess Docker gave up on Swarm?

Curious to know why you think so? ECS is a managed service. If Swarm was a managed service on AWS, I'd agree with you here but that's not the case. Swarm is still brilliant for running multi-node deployments.

Mirantis purchased Docker Enterprise at a firesale price last year. They've pledged support for two years, and they say they will be "continuing to invest in active Swarm development," but the writing is probably on the wall. Their release was more excited about K8s.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#22

Post by mcintyre1994 »

ramraj07 wrote: post #12
mcintyre1994 wrote: post #9

Earlier quoted context omitted.

We’re thinking about doing a similar migration. One of my concerns is that the current Beanstalk infra isn’t described in code, and when I’ve experimented a little with Beanstalk in CloudFormation it’s been horrible to write - for something a lot simpler. I obviously want us to move to using CloudFormation or something like it if we migrate, how good or bad would you say using it (or Terraform if that’s what you sett…

Have you considered experimenting with AWS CDK? The code looked far more elegant than cloudformation

I have done a tiny bit, probably worth trying to move some smaller CFN templates over to it in earnest to try it out a bit more. I can definitely see it being nicer for things like Beanstalk/Fargate.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#23

Post by mrgordon »

BjoernKW wrote: post #8
scarface74 wrote: post #4

Earlier quoted context omitted.

How do you have a “standard” without each provider having to wait on a committee anytime they want any improvements? Even the almighty Terraform which for some reason people still think makes it easy not to experience “cloud lock-in” has cloud specific provisioners.

In my opinion, being cloud-agnostic is today’s being database-agnostic. In more than two decades of professional software development, I have only once encountered a situation where an existing application was migrated to a different RDBMS instead of just being rewritten. Using an ORM framework for the sake of database independence seems hardly justified in that case. I suppose that things will turn out much the same…

I mostly agree with you but we definitely reduced reliance on AWS specific functionality after starting to offer on-premise software installations. Most of them don’t gain you THAT much and then the software really isn’t very portable.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#24

Post by Traubenfuchs »

jhatemyjob wrote: post #11

I never understood why people use Docker. QEMU exists

Whether it was luck or hard facts, Docker became the standard and default nearly to a point where juniors only knowing how to program a "Hello World!" webservice will dockerize it. It's an ubiquitous technical skill like basic SQL.

As someone who has very low interest in container technology itself, I have zero reason to inform myself about QUEMU..

Re: Docker Releases Plugin for Simplified Deployments into AWS

#26

Post by imsodrunklol »

irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

I just want to mention that you can output the CloudFormation template that it parses out by saying `docker ecs compose convert`, which is always handy. You also could use other flags to help with joining clusters, services ,etc. Not saying it's a complete production ready too, but it is nice tool to help speed up the process.

https://docs.docker.com/engine/context/ecs-integration/

Re: Docker Releases Plugin for Simplified Deployments into AWS

#27

Post by nostrebored »

irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

I highly recommend the CDK here. A setup very similar to yours is just a few lines of code which you can synth into cloudformation templates

Re: Docker Releases Plugin for Simplified Deployments into AWS

#29

Post by simo7 »

ramraj07 wrote: post #13
irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

Could you comment on why you are moving away from elastic beanstalk? We manage a fairly simple EB deployment but it seems perfect for our infra needs, and I'm not able to imagine why we might need to scale out of it - if any other services are required, I'm tempted to only launch multiple EB deployments instead of going the kubernetes/fargate route.

For us it's the following reasons:

* It's more cost effective to place all the services on one cluster. As containers can share the instance resources it's easier to increase resource utilisation (not true w/ Fargate though).

* Support for new features on EB can be quite delayed. Eg. we need support for ALPN policies, it's a recent feature and it's not even in CloudFormation yet. With ECS we just manage the LB directly and we can do everything the API allows us to do.

* More granular control. Eg. during rolling updates we can decide a floor to how many containers are active at a given time (many others things like this).

* Integration w/ SSM and Secrets Manager.

* Better IaaS support (with EB everything happens in configuration files outside of Terraform or Cfn resources).

Re: Docker Releases Plugin for Simplified Deployments into AWS

#30

Post by solarist »

oblio wrote: post #28
smetj wrote: post #25

Just eat the frog and learn Terraform or Cloud formation.

> eat the frog Eat the frog? Which language is that? The expression sounds really cool! Most of the time in English I've encountered "bite the bullet".

Have you heard of Mark Twain by any chance? People say he used to write in English.
Post reply on HN