I'm trying to get more into micro-service architecture, discovering and using this image has made my life easier, the virtual host setup makes it super easy to have any amount of services running under this load balancer's rule. However I was watching this video from pycon this year where they split a toy flask application into micro-services, the presenter makes it clear that besides the load balancer one needs a service registry to feed the load balancer. However with haproxy the load balancer is feed out of docker itself, so:
Does dockercloud-haproxy defeat the purpose of setting up a service registry?
Does it combine a load balancer and a service registry?
In docker clouds case it is the service registry. You define your services etc.. in your stacks etc... and haproxy feeds of that configuration. At least thats the way I view it :)
I'm trying to get more into micro-service architecture, discovering and using this image has made my life easier, the virtual host setup makes it super easy to have any amount of services running under this load balancer's rule. However I was watching this video from pycon this year where they split a toy flask application into micro-services, the presenter makes it clear that besides the load balancer one needs a service registry to feed the load balancer. However with haproxy the load balancer is feed out of docker itself, so:
dockercloud-haproxy
defeat the purpose of setting up a service registry?