From ae8d7b46138bb48ce6847041142c36b284c7381b Mon Sep 17 00:00:00 2001 From: Magnus Kulke Date: Wed, 12 Oct 2016 00:15:53 +0200 Subject: [PATCH] Added ELB/ALB, alternatives to ECS section --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ae8c2fe4..220e6877 100644 --- a/README.md +++ b/README.md @@ -879,7 +879,6 @@ ALB - ALBs do not (yet) support routing based on HTTP “Host” header or HTTP verb. - Instances in the ALB's target groups have to either have a single, fixed healthcheck port (“EC2 instance”-level healthcheck) or the healthcheck port for a target has to be the same as its application port (“Application instance”-level healthcheck) - you can't configure a per-target healthcheck port that is different than the application port. - ALBs are VPC-only (they are not available in EC2 Classic) -- In a target group, if there is no healthy target, all requests are routed to all targets. An example: you add a target group containing a single service (with a long init phase maybe) as target to a listener, it does not pass health checks (yet), requests will still reach your (initializing) service. Elastic IPs ----------- @@ -983,11 +982,17 @@ ECS - Doesn’t support cross-region replication of images. - If you want fast fleet-wide pulls of large images, you’ll need to push your image into a region-local registry. - Doesn’t support custom domains / certificates. +- A container's health is monitored via [CLB](#clb) or [ALB](#alb). Those can also be used to address a containerized service. When using an ALB you do not need to handle port contention (i.e. services exposing the same port on the same host) since an ALB’s target groups can be associated with ECS-based services directly. ### ECS Tips - [This blog from Convox](https://convox.com/blog/ecs-challenges/) (and [commentary](https://news.ycombinator.com/item?id=11598058)) lists a number of common challenges with ECS as of early 2016. +### ECS Alternatives and Lock-in + +- [Kubernetes](https://kubernetes.io): Extensive container platform. Available as a hosted solution on Google Cloud (https://cloud.google.com/container-engine/) and AWS (https://tectonic.com/). +- [Nomad](https://www.nomadproject.io/): Orchestrator/Scheduler, tightly integrated in the Hashicorp stack (Consul, Vault, etc). + 🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md) Lambda