4 ms·

I'd be really interested to know more about how this compares and contrasts to Elastic Beanstalk (EBS)? particularly the docker flavours of EBS. I've looked th

I'd be really interested to know more about how this compares and contrasts to Elastic Beanstalk (EBS)? particularly the docker flavours of EBS. I've looked through a couple of the previous threads and didn't find much on this.

avitzurel 10y ago
Using ElasticBeanstalk you still need to "handle" environments, applications. This is a level of abstraction above ECS, which Beanstalk uses behind the scenes for multi-container installations. If you think about it, it's like Heroku for docker, you handle "apps", and the rest is handled by Rack. This is how I understand it.
nzoschke 10y ago
I'd say Elastic Beanstalk is the most direct "competition" because it his the same points: * Simple * Configures AWS resources uniformly run your app * Uses Docker Some advantages to using Convox instead of Elastic Beanstalk: * More flexibility in the experience. Convox has a simpler API and CLI for end users. * More flexibility in the infrastructure. We can pick and choose the best infrastructure components and constantly evolve. * Less lock in. This is speculative but having a thin layer between you and AWS could help with portability.
- kolanos 10y ago
  I also consider use of docker's own toolchain (docker-compose, docker-machine) to a be a big plus as well. EB has very much an NIH feel with all the JSON manifests and such.
- nzoschke 10y ago
  The biggest difference is that Convox is Convox... AWS is awesome but their values might not exactly align with your organization. There are general advantages to letting the Convox team and community guide you through your cloud journey. We value developer experience where AWS simply doesn't. Our plans include things AWS will never add to EBS like automating dashboards, monitoring and alerts. We are moving a lot faster. Convox has swap and CloudWatch Logs integration where ECS doesn't.

avitzurel 10y ago

Using ElasticBeanstalk you still need to "handle" environments, applications. This is a level of abstraction above ECS, which Beanstalk uses behind the scenes for multi-container installations. If you think about it, it's like Heroku for docker, you handle "apps", and the rest is handled by Rack. This is how I understand it.

nzoschke 10y ago

I'd say Elastic Beanstalk is the most direct "competition" because it his the same points: * Simple * Configures AWS resources uniformly run your app * Uses Docker Some advantages to using Convox instead of Elastic Beanstalk: * More flexibility in the experience. Convox has a simpler API and CLI for end users. * More flexibility in the infrastructure. We can pick and choose the best infrastructure components and constantly evolve. * Less lock in. This is speculative but having a thin layer between you and AWS could help with portability.

kolanos 10y ago
I also consider use of docker's own toolchain (docker-compose, docker-machine) to a be a big plus as well. EB has very much an NIH feel with all the JSON manifests and such.
nzoschke 10y ago
The biggest difference is that Convox is Convox... AWS is awesome but their values might not exactly align with your organization. There are general advantages to letting the Convox team and community guide you through your cloud journey. We value developer experience where AWS simply doesn't. Our plans include things AWS will never add to EBS like automating dashboards, monitoring and alerts. We are moving a lot faster. Convox has swap and CloudWatch Logs integration where ECS doesn't.