24 engineers on Hacker News describe using Amazon Elastic Load Balancing first-hand: 3 endorse it, 9 regret it, 0 are mixed.
“ALBs didn't work at the scale we needed them to, so we run our own caddy instances.”
regret · production · mooreds · 2025-02-18 · source ↗ · wrong label?“Classic ELB (back in the day) needed quite a lot of preemptive poking and fake generated traffic to be able to ramp up capacity fast enough”
regret · production · bigiain · 2020-07-08 · source ↗ · wrong label?“We switched TLS termination from the load balancer to Envoy + cert-manager and the results were much better.”
regret · production · jrockway · 2019-12-13 · source ↗ · wrong label?“ELB works better than Google Cloud load balancer which had random issues and meltdowns when we were there. Also support is better.”
endorse · production · eknkc · 2017-11-29 · source ↗ · wrong label?“we use them at work all the time for services like ELB, that do not give you a lot of details”
regret · production · vaishaksuresh · 2016-12-22 · source ↗ · wrong label?“connections to the elb were rejected despite the metrics never indicating a problem”
regret · production · 1.5 yr · encoderer · 2016-08-11 · source ↗ · wrong label?“And we use ELBs for load balancing and routing.”
endorse · production · nzoschke · 2015-08-02 · source ↗ · wrong label?“the deep integration between things like autoscaling groups, EC2, ELB, etc makes it easy to automate all the things”
endorse · production · NathanKP · 2015-07-09 · source ↗ · wrong label?“It caused our ELB to fail all the instances even if we brought up new ones. Also during load you can get other sites to show up on your ELB.”
regret · production · adrr · 2013-11-27 · source ↗ · wrong label?“Typical pain points are lack of flexibility in ELBs and variable performance on EBS - nothing that can't be worked around.”
regret · production · mryan · 2013-01-29 · source ↗ · wrong label?“We switched away from ELBs because of this dependency.”
regret · production · helper · 2012-10-27 · source ↗ · wrong label?“We are using it and are about to get rid of it. The main problem is what exactly happened last night.”
regret · production · explodingbarrel · 2012-06-30 · source ↗ · wrong label?“how to use a sentry trace id to find a otel traceparent, where my ALB is”
neutral · production · hadlock · 2026-09-08 · source ↗ · wrong label?“In Prod, we use a CDN to server the static files using AWS ALB and Cloudfront.”
neutral · production · Cshelton · 2025-07-04 · source ↗ · wrong label?“we ended up migrating terminating HTTPS on AWS's ELB”
neutral · production · engine_y · 2025-02-17 · source ↗ · wrong label?“The API Gateway and ALB code was pretty much a one-and-done”
neutral · production · 2 yr · fivea · 2021-11-20 · source ↗ · wrong label?“shifted to a nlb with tls termination in app.”
neutral · production · tasssko · 2021-03-18 · source ↗ · wrong label?“we put behind a AWS LB so we can push partial traffic to our experiment”
neutral · production · social_quotient · 2020-07-12 · source ↗ · wrong label?“selected it from a drop down on the ALB where it was needed.”
neutral · production · jillesvangurp · 2019-08-13 · source ↗ · wrong label?“the ALB not having their request-timeouts set to to the same value.”
neutral · production · vanrysss · 2019-02-23 · source ↗ · wrong label?“we failed requests for several minutes before we decided to just switch back to the old ELB then ask them to do a prewarming”
neutral · production · callalex · 2017-08-23 · source ↗ · wrong label?“3 ELBs sit in front of those servers, all in a VPC.”
neutral · production · themartorana · 2016-06-12 · source ↗ · wrong label?“We run a pretty standard setup with ELB, Postgres (master/replica), webservers and job processing servers.”
neutral · production · roncohen · 2014-10-23 · source ↗ · wrong label?“We use ELB (Elastic Load Balancer) with an auto-scaling group behind it.”
neutral · production · bad_user · 2013-06-04 · source ↗ · wrong label?