Earlier quoted context omitted.
I was primarily referring to EC2.
Why do you need IPv6? It seems pretty unnecessary in a VPC.
> Starting June 1, 2016 all apps submitted to the App Store must support IPv6-only networking.
71–80 of 140 posts
Earlier quoted context omitted.
I was primarily referring to EC2.
Why do you need IPv6? It seems pretty unnecessary in a VPC.
> Starting June 1, 2016 all apps submitted to the App Store must support IPv6-only networking.
Earlier quoted context omitted.
Yes, Google's load balancer is the best one available today. The lack of native websockets support is probably the only disadvantage but made up for with the scaling abilities and cross-region support. ALB pricing is strange too, classic AWS style complexity.
The Google load balancer supports proxy websockets over SSL (wss://) with the SSL Proxy mode: https://cloud.google.com/compute/docs/load-balancing/tcp-ssl...
Earlier quoted context omitted.
Google's load balancer does do HTTP/2. It doesnt have native websocket protocol support (you have to use the network LB for that traffic) but it does provide cross-region balancing.
Websockets over SSL is in beta: https://cloud.google.com/compute/docs/load-balancing/tcp-ssl...
AWS still doesn't support IPv6. Good to see them talking about HTTP/2. Waiting for AWS to embrace IPv6.
Earlier quoted context omitted.
BTW, is there any place to log feature requests?
Become a big enough customer
It seems like the number of customers asking for a feature is more important than the size of those customers in my experience.
Does anyone know if it (finally) supports sticky websocket sessions?
For a single connection the websocket will always go to the same back end regardless of sticky sessions being enabled.
If stickyness is enabled, and the same client creates a new websocket, it will go to the same back end as previous connections.
AWS still doesn't support IPv6. Good to see them talking about HTTP/2. Waiting for AWS to embrace IPv6.