Haproxy - Tag - Filipe Felisbinohttps://felisbino.dev/tags/haproxy/Haproxy - Tag - Filipe FelisbinoHugo -- gohugo.ioenSat, 10 Sep 2016 00:00:00 +0000Docker: Service discovery for docker containers on AWShttps://felisbino.dev/posts/docker-service-discovery-on-aws/Sat, 10 Sep 2016 00:00:00 +0000Filipe Felisbinohttps://felisbino.dev/posts/docker-service-discovery-on-aws/<p>These days we see lots of fancy ways to do service discovery with docker. You see examples of people using etcd, zookeeper, consul and so on. I recently had a project to migrate some solr clusters to docker and I started looking at some of those tools and how they would fit that our current infrastructure.</p> <p>After some researching I found that the KISS way of doing service discovery on our environment was to use route53. The main reasons for this decision were:</p>AWS custom-crafted load balancer with haproxyhttps://felisbino.dev/posts/aws-load-balancer/Sat, 06 Aug 2016 00:00:00 +0000Filipe Felisbinohttps://felisbino.dev/posts/aws-load-balancer/Today’s tip is on how to launch a custom-crafted load balancer on AWS as a replacement for ELBs.

Motivation

First of all I need to say that I love AWS’ ELB. It is cost-effective and works just fine for most of the cases.

So why would I create a custom-crafted ELB? Well, there are some features that AWS’ ELB just don’t support. Things like:

  • A static IP or elastic IP entry point
  • UDP load balancing
  • Customized balancing strategy
  • Custom backend routing
  • One load balancer for multiple backends
  • SNI resolution(SSL routing)

So if the ELB is not suited for your use case, do it yourself :-)

]]>