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

Migrating from Heroku to AWS using Docker

blog.doordash.com

Post reply on HN
Print view View original

21–30 of 58 posts

Re: Migrating from Heroku to AWS using Docker

#21

Post by kudu »

philip1209 wrote: post #16
madeofpalk wrote: post #9

If you're looking at doing this, especially if you're moving from Heroku and/or using Docker, seriously consider AWS ElasticBeanstalk. http://aws.amazon.com/elasticbeanstalk/ In case you don't know, ElasticBeanstalk is the AWS Heroku but _a lot_ more flexible. It's basically a layer on top of EC2 and ELB. It takes care of creating auto-scaled EC2 instances to your specification and deploying your application to it (w…

It's worth noting that Elastic Beanstalk just released support for multiple docker containers per instance. This takes EBS from being a novelty to being production-grade Docker orchestration. Previously, it ran a single docker container per instance which - while good for stage/prod parity and easy rollbacks - doesn't really take advantage of the core Docker advantages over a VM. Now, you can orchestrate multiple con…

> (Note - here EBS = elastic beanstalk, not elastic block storage)

I, really, really don't recommend using EBS as an abbreviation for Elastic Beanstalk, since Amazon uses the actual abbreviation canonically to refer to Elastic Block Storage. At worst, just call it Beanstalk, when the AWS context is clear.

Re: Migrating from Heroku to AWS using Docker

#22

Post by philip1209 »

coenhyde wrote: post #20
philip1209 wrote: post #16

Earlier quoted context omitted.

It's worth noting that Elastic Beanstalk just released support for multiple docker containers per instance. This takes EBS from being a novelty to being production-grade Docker orchestration. Previously, it ran a single docker container per instance which - while good for stage/prod parity and easy rollbacks - doesn't really take advantage of the core Docker advantages over a VM. Now, you can orchestrate multiple con…

You should do a blog post. I had no idea Elastic Beanstalk allows multiple docker containers per instance. This changes EVERYTHING! I would love to hear how you got this all tied together.

Here's the announcement - it's a little over a week old:

https://aws.amazon.com/about-aws/whats-new/2015/03/aws-elast...

Re: Migrating from Heroku to AWS using Docker

#23

Post by brucer »

andyfang wrote: post #13
madeofpalk wrote: post #9

If you're looking at doing this, especially if you're moving from Heroku and/or using Docker, seriously consider AWS ElasticBeanstalk. http://aws.amazon.com/elasticbeanstalk/ In case you don't know, ElasticBeanstalk is the AWS Heroku but _a lot_ more flexible. It's basically a layer on top of EC2 and ELB. It takes care of creating auto-scaled EC2 instances to your specification and deploying your application to it (w…

That's definitely something we considered doing at DoorDash. I've heard bad things about it as you want more control over deployment/package upgrades, etc. how has that played out for you?

I'm also curious if any large projects use it. We tried it out for a couple weeks - it worked fine but we felt overly constrained by the configuration rules and ended up rolling our own solution.

Re: Migrating from Heroku to AWS using Docker

#24

Post by philip1209 »

kudu wrote: post #21
philip1209 wrote: post #16

Earlier quoted context omitted.

It's worth noting that Elastic Beanstalk just released support for multiple docker containers per instance. This takes EBS from being a novelty to being production-grade Docker orchestration. Previously, it ran a single docker container per instance which - while good for stage/prod parity and easy rollbacks - doesn't really take advantage of the core Docker advantages over a VM. Now, you can orchestrate multiple con…

> (Note - here EBS = elastic beanstalk, not elastic block storage) I, really, really don't recommend using EBS as an abbreviation for Elastic Beanstalk, since Amazon uses the actual abbreviation canonically to refer to Elastic Block Storage. At worst, just call it Beanstalk, when the AWS context is clear.

We use beanstalkd queue too (SQS gets expensive at scale!), so "beanstalk" is unfortunately also equivocal in our infrastructure. I think it's just bad naming for AWS Elastic Beanstalk overall.

Re: Migrating from Heroku to AWS using Docker

#27

Post by rdoherty »

philip1209 wrote: post #22
coenhyde wrote: post #20

Earlier quoted context omitted.

You should do a blog post. I had no idea Elastic Beanstalk allows multiple docker containers per instance. This changes EVERYTHING! I would love to hear how you got this all tied together.

Here's the announcement - it's a little over a week old: https://aws.amazon.com/about-aws/whats-new/2015/03/aws-elast...

I think he meant a blog post about your entire architecture and build/deployment would be great. And I agree :)

Re: Migrating from Heroku to AWS using Docker

#30

Post by singlow »

riffraff wrote: post #19
reustle wrote: post #4

Did you know your site was blocked in Indonesia? > This site is prohibited. The site is included in the list that should not be accessed through this network because contains porn, gambling, phising/malware, SARA or Proxy. > In accordance with Indonesian Government Regulation refers to Law Number 36 of Year 1999 on Telecommunications Article 21, "Telecommunication provider is prohibited from conducting business telec…

what is SARA?

An acronym that is code word for ethnic, religious, tribal, and racial issues that are not to be discussed publicly and are censored by the ministry of information.

https://books.google.com/books?id=2oZQRuT78JIC&pg=PA80&lpg=P...

Post reply on HN