The question is... does HTTP/2 on the backend help that much. We aren't restricted like a browser in terms of bandwidth, latency or number of connections we can open. Greatest benefit for HTTP/2 is between browser and us, but origin HTTP/2 hasn't been forgotten.
My ideal situation is one where I can have my webapp specify it's dependencies through a spec such as Server Hints[1], and have them be requested and cached edge-side, turned into a Server Push to the end user.
[1]: https://www.chromium.org/spdy/link-headers-and-server-hint/l...
Seems like for high traffic sites and APIs the persistent non-blocking multiplexed connections with binary transfer might make a big difference?
I think Instart Logic uses the same kind of model in between their proxy nodes called IPTP (inter-proxy transport protocol).