5 ms·
Firstly: not very new. Hasn't Netflix been at this for a long time? Secondly, everyone should be checking. Not only is Google doing a lot of subsidization, but
by KirinDave 9y ago
Firstly: not very new. Hasn't Netflix been at this for a long time?
Secondly, everyone should be checking. Not only is Google doing a lot of subsidization, but their services are really really good. My current employer ended up being unable to use them but it's I acutely regret every day I'm forced to build out things Google already has or deal with Amazon's frustratingly antiquated ELB infrastructure.
- archgoon 9y agoWhat are the problems you've been running into with ELB?
- dalyons 9y agoNo http2 support is increasingly limiting
- bradhe 9y agoALB has HTTP2 support.
- mwarkentin 9y agoOnly at the front end, it downgraded to 1.1 between the ALB and your servers.
- manigandham 9y agoAll load balancing services do that today. It is rare to get HTTP/2 on both ends unless you run your own software like Envoy.
- joevandyk 9y agoI’m sure you are aware but AWS has a newish loaf balancer now: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html https://docs.aws.amazon.com/elasticloadbalancing/latest/appl...
- chrisweekly 9y agoloaf -> load, lol
- tracker1 9y agoIt's the best thing since sliced bread after all.
- Cshelton 9y agoAWS's ELB/ALB have been rock solid for us. Not sure what you are referring to when you say 'antiquated infrastructure'?
- cptskippy 9y agoAntiquated doesn't mean unstable or unusable. It means old fashioned. It's not the new hotness.
- KirinDave 9y agoI see such intense benefits from HTTP/2 end to end, I'm quite happy to be called a shiny-chaser when my 50th and 99th drops so sharply. Also, prefetch is absolutely incredible for webapps and I'm trying to get my peers at my current employer to embrace it even if it's not well supported in AWS.
- web007 9y agoHave you tried termination at ELB with TCP to backend, or just plain TCP passthrough all the way? Also as mentioned elsewhere, ALB or NLB might do what you want, either working the same way as regular ELB or via the same workarounds.
- KirinDave 9y agoTo answer your question directly, AWS's poor spike handling has really made me distrustful of them. It's not that AWS's support staff is bad (actually, they're phenomenal given the difficulty of that job) but... the fact that I can be taken down by a big scale event because I can't pre-scale my ELBs without support help that takes hours is kinda annoying. Now, I've been TOLD by ___________________________________ this is actually because it's a pain in the butt and they're working to fix it, but AWS's budget seems to favor new shinies over iterating on the existing environment. Look how long it took us to get a new and less buggy AWS dashboard and that still hasn't propagated to all the internal services. I could go on. For example, my experience is that GCE's and even Azure's I/O and networking is way faster, more consistent and more reliable than AWSs. I host all my dev boxes on GCE because using an attached drive (so I can de/re-provision to save on costs) is much less agonizing. Also: google has some AMAZING database products that category kill whole infrastructure tasks. It's a very good kind of vendor lock-in when they can say, "You can't move away because no one else has found a way to provide our feature set."
- mrits 9y agoOne of the reasons I don't like working on GCP or Azure is because I prefer ELB.