3 ms·
Have been waiting for this for awhile. However, is needing to "warm up" the load balancer to deal with sudden spikes still an issue? This was a deterrent to goi
by tsukaisute 10y ago
Have been waiting for this for awhile. However, is needing to "warm up" the load balancer to deal with sudden spikes still an issue? This was a deterrent to going all-in on the ALB despite other benefits (SSL termination, etc.)
Also, wondering if there any obvious cons (perhaps performance?) to using one ALB to handle multiple routes vs. separating them.
- randerson 10y agoI asked one of Amazon's ELB Product Managers this a few months ago and was told that no, there's no longer a need to warm up an ELB/ALB except perhaps in extreme cases.
- tsukaisute 10y agoWow, if so, this should be "front and center" news. This best practices page [1], upd. 2014 still talks about "Pre-Warming" Tangent: I wonder how often we utilize outdated "truths" in our best practices. For example, the "you must minimize the number of assets" rule was obsoleted with HTTP/2, but will probably take years to take hold. [1] https://aws.amazon.com/articles/1636185810492479 https://aws.amazon.com/articles/1636185810492479
- hossbeast 10y agoThe correct term is "priming"
- NathanKP 10y agoAWS employee here. You are welcome to check with AWS Support based on your predicted traffic load for extra assurance, but in my experience the new ALB no longer requires priming, even for significant traffic spikes. If any of you are going to Dockercon in Austin stop by the AWS booth and I'd be happy to show you a demo app that uses an ALB with about ten rules to route traffic to different microservices running as tasks under EC2 Container Service. The demo includes a load test to drive traffic to the ALB and the services behind the ALB, verifying the consistent performance as traffic scales up.