AWS Elastic Load Balancing (ELB) vs Hipache: What are the differences?

Developers describe AWS Elastic Load Balancing (ELB) as "Automatically distribute your incoming application traffic across multiple Amazon EC2 instances". With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task. On the other hand, Hipache is detailed as "A distributed HTTP and websocket proxy". Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second. It is particularly well-suited for PaaS (platform-as-a-service) and other environments that are both business-critical and multi-tenant.

AWS Elastic Load Balancing (ELB) and Hipache belong to "Load Balancer / Reverse Proxy" category of the tech stack.

"Easy" is the top reason why over 46 developers like AWS Elastic Load Balancing (ELB), while over 2 developers mention "Redis as backend" as the leading cause for choosing Hipache.

Hipache is an open source tool with 2.25K GitHub stars and 264 GitHub forks. Here's a link to Hipache's open source repository on GitHub.