LinuxCon + ContainerCon North America 2016

Microservice Applications bring many powerful benefits -- scalability, component isolation, and a much simpler platform for feature updates and additions. In many respects, these benefits are enabled by splitting the functional components of an application apart into separate services and using the network as the mechanism for interprocess communication. While this fundamental change in application architecture has many benefits, it also has some inherent problems: it is difficult to link components together, make them secure and make them performant.

Loadbalancers facilitate scale-out and resiliency for the front-tier of an application and can enhance the performance of SSL-secured endpoints. An emerging trend is to use load balancers for all layers of the application. These load balancers bring valuable new capabilities in resilience (throttling, circuit breakers), enabling continuous deployments (routing or content switching), visibility (tracing, debug, anomaly detection), and compliance to a microservices based deployment. These are sometimes embedded in the microservice (e.g., Netflix Ribbon) and sometimes as a sidecar (AirBnB Synapse), or alternatively, deployed as Containers. Containerized Load Balancers are a perfect fit for some of these jobs, especially in the context of K8s, Swarm and ECS. The talk will discuss these container deployment architectures and point the way forward to new use cases (multi-Cloud, SDN, security)

You proudly created a modern microservices app, packaged it with Docker, used Consul as service registry and deployed it on Mesos/Marathon and it was fast and super easy! Now you want to put a reverse proxy in front of it... And you have to write ugly hacks :(
Why don't we create a modern reverse proxy in GO that would support several backends (Docker, Mesos/Marathon, Kubernetes, Consul, Etcd, Zookeeper, BoltDB, Rest API, file…) to manage its configuration automatically and dynamically?