3

Is there a way to systematically clone/scale Docker containers as microservices so that a bottleneck caused by too few instances of a particular container type(web, routing, database, etc.) is eliminated?

That the system essentially reconfigure itself by responding to different load profiles. Also that containers in the system are discoverable and in communications as services.

If this was on an EC2 instance, that it also know when system resources were maxed and use Weave to connect the new containers in a newly AWS scaled instance to balance load? on NodeJS.

Mark Simon
  • 612
  • 1
  • 6
  • 17
  • Can you use ELBs and auto scaling groups with appropriate policies? – scrowler Jun 17 '15 at 09:59
  • I'm *trying* to build such a thing in [autodock](https://github.com/prologic/autodock) and the new plugin autodock-autoscale (*not published yet*). – James Mills Jun 17 '15 at 10:18
  • Also an an aside; I've found in my experience AWS's ELB(s) and Auto Scaling facilities quite slow and don't really scale instantaneously like many Docker-based solutions like hipache. – James Mills Jun 17 '15 at 10:19
  • You could probably bake your own ASG using CloudWatch alarms and their API – scrowler Jun 18 '15 at 05:45
  • We have an new guide that might of interest: http://weave.works/guides/service-discovery-with-weave-aws-ecs.html – errordeveloper Aug 21 '15 at 11:33

0 Answers0