Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Application Load Balancer

aws.amazon.com

Post reply on HN
Print view View original

41–50 of 140 posts

Re: AWS Application Load Balancer

#41

Post by cheald »

mattlong wrote: post #36
indale wrote: post #21

This looks pretty sweet. The next big thing for api versioning would be header instead of url based routing, looking forward to 'give you access to other routing methods'.

Already has it! "An Application Load Balancer has access to HTTP headers and allows you to route requests to different backend services accordingly." Edit: On a second read, it's less clear if header based routing is actually available yet...

It only allows you to route via path matching right now.

"each Application Load Balancer allows you to define up to 10 URL-based rules to route requests to target groups. Over time, we plan to give you access to other routing methods."

The ALB clearly has technical access to the headers, but use of them isn't exposed to users yet.

Re: AWS Application Load Balancer

#42

Post by cheald »

snug wrote: post #40
cheald wrote: post #31

Exciting! Disappointing that you can't route based on hostname yet, though. I've got 5 ELBs set up to route to different microservices for one app, and because we couldn't do path-based routing before, that's all segmented by hostname. As soon as ALB supports hostname routing, I can collapse those all into a single LB.

The "Hostname" is in the HTTP Header, "Host." The article states that you can route based on Layer 7 headers, so this shouldn't be an issue.

Yeah, but they only allow you to route via path matching right now. The ALB has access to the headers, but configuring it based on arbitrary headers isn't exposed to end users yet.

I excitedly set up an ALB as soon as I read the post, because I've needed it, only to find that support for what I want isn't available to me yet!

Re: AWS Application Load Balancer

#43

Post by MrMullen »

encoderer wrote: post #38

We plan to do a blog post about this at some point, but we had the pleasure of seeing exactly how elastic the elb is when we switched Cronitor from linode to aws in February 2015. Requisite backstory: Our api traffic comes from jobs, daemons, etc, which tend to create huge hot spots at tops of each minute, quarter hour, hour and midnight of popular tz offsets like UTC, us eastern, etc. There is an emergent behavior t…

This is actually fairly common. ELB scales up as your traffic scales up but it can not handle tsunami levels of traffic. It can only handle incremental level increases of traffic. You have to contact Amazon support to get them to fix your ELB at a larger instance for the entire life of the instance.

One the major down sides of Amazon AWS.

Re: AWS Application Load Balancer

#45

Post by erikcw »

I'm curious if this will Convox to route to multiple services with just a single ALB instead of the historical default of 1 ELB per service. Would be a real cost savings for a micro-services architecture.

Re: AWS Application Load Balancer

#48

Post by bgentry »

encoderer wrote: post #38

We plan to do a blog post about this at some point, but we had the pleasure of seeing exactly how elastic the elb is when we switched Cronitor from linode to aws in February 2015. Requisite backstory: Our api traffic comes from jobs, daemons, etc, which tend to create huge hot spots at tops of each minute, quarter hour, hour and midnight of popular tz offsets like UTC, us eastern, etc. There is an emergent behavior t…

I was coming here to ask whether pre-warming is still an issue with the ALB service. Maybe jeffbarr can comment on whether that's changed?

GCE's load balancer does not use independent VM instances for each load balancer, instead balancing at the network level. So you can instantly scale from 0 to 1M req/s with no issues at all.

Re: AWS Application Load Balancer

#49

Post by bgentry »

erikcw wrote: post #45

I'm curious if this will Convox to route to multiple services with just a single ALB instead of the historical default of 1 ELB per service. Would be a real cost savings for a micro-services architecture.

It should allow Convox to do that, yes. Although it doesn't appear (from the screenshots) that you can route by Host header, so you'd have to put all your services on the same hostname with different path prefixes to make it work.
Post reply on HN