4 ms·
I actually view HTTP/2 as a great equalizing force for smaller players: It is perfect for "hiding" latency, so you are not forced to use a CDN like Cloudflare j
by heipei 6y ago
I actually view HTTP/2 as a great equalizing force for smaller players: It is perfect for "hiding" latency, so you are not forced to use a CDN like Cloudflare just to be closer to your user.
Example: I run a service without a CDN, but I only host it on dedicated servers located in Europe. Per-request latency is OKish for users in the US, but my service makes dozens of subrequests to the same origin when loading pages (images, XHR calls). Without HTTP/2, the user-experience for US customers would be abysmal and I'd be forced to reach for a CDN which has a PoP closer to them.
- heipei 6y agohttps://http2.golang.org/gophertiles?latency=200 https://http2.golang.org/gophertiles?latency=200 and https://http1.golang.org/gophertiles?latency=200 https://http1.golang.org/gophertiles?latency=200 perfectly demonstrate the issue I'd be facing otherwise. 200ms latency from the US West Coast to Europe is realistic, and the number of subresources being requested is also realistic for my application. If you don't believe the latency, try services like these: https://cloudpingtest.com/digital_ocean https://cloudpingtest.com/digital_ocean and https://pingtestlive.com/digitalocean-ping https://pingtestlive.com/digitalocean-ping