I'm assuming their thought process went like this: "we want to optimize a workflow which today goes over HTTP RPC/REST for mobile networks where the retry behavior of TCP at the low level is suboptimal. QUIC already exists, and we don't have to figure out our own solutions to firewalls, security, HTTP semantics. Also our webapps use the same or similar API endpoints, so the less effort spent writing new routing, monitoring, etc., the better. Oh, it works really well. Awesome, avoided 6-24 months debugging a custom protocol over mobile networks around the world that we don't control."
Comments
I'm assuming their thought process went like this: "we want to optimize a workflow which today goes over HTTP RPC/REST for mobile networks where the retry behavior of TCP at the low level is suboptimal. QUIC already exists, and we don't have to figure out our own solutions to firewalls, security, HTTP semantics. Also our webapps use the same or similar API endpoints, so the less effort spent writing new routing, monitoring, etc., the better. Oh, it works really well. Awesome, avoided 6-24 months debugging a custom protocol over mobile networks around the world that we don't control."