title: optimize rest API for HTTP/2 or HTTP/3
body: <p>I found out from <em>multiple sources</em><sup> <a href="https://docs.google.com/presentation/d/1r7QXGYOLCh4fcUq0jDdDwKJWNqWK1o4xMtYpKZCJYjM/edit#slide=id.p19" rel="nofollow noreferrer">1</a> <a href="https://livebook.manning.com/book/http2-in-action/chapter-6/" rel="nofollow noreferrer">2</a> <a href="https://blog.cloudflare.com/http-2-for-web-developers/" rel="nofollow noreferrer">3</a> <a href="https://www.smashingmagazine.com/2016/02/getting-ready-for-http2/" rel="nofollow noreferrer">4</a> <a href="https://unused-css.com/blog/what-http2-means-for-frontend-development/" rel="nofollow noreferrer">5</a> <a href="https://medium.com/swlh/http-2-and-website-optimization-b919cd0de7b5" rel="nofollow noreferrer">6</a> <a href="https://yoast.com/performance-optimization-http2/" rel="nofollow noreferrer">7</a> <a href="https://hpbn.co/optimizing-application-delivery/#optimizing-for-http2" rel="nofollow noreferrer">8</a> <a href="https://www.makeuseof.com/tag/ways-improve-websites-pagespeed-using-http2/" rel="nofollow noreferrer">9</a></sup> that we do not need to do the following to optimize our rest API for HTTP/2 or HTTP/3:</p>
  <ol>
  <li>domain sharding</li>
  <li>concatenating assets</li>
  <li>inlining assets</li>
  <li>turning multiple image files into sprites</li>
  <li>not inline images in CSS using data URIs</li>
  </ol>
  <p>However, I am not sure if this is the complete picture. is there anything more to optimize our rest API for HTTP/2 or HTTP/3? Is there any more benefits we can have as a web developer when using HTTP/2 or HTTP/3?</p>
  <p>Just to be clear, i am not talking about backward compatibility or anything. I just want to know - if I am sure my API will be served using HTTP/2 or HTTP/3 and my API will only be accessed by clients who support HTTP/2 or HTTP/3 then what optimizations / benefits (things I do not have to do anymore) can I have.</p>
  <p>One more thing. Chromium developers have <a href="https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ?pli=1" rel="nofollow noreferrer">announced</a> that they plan to remove support for HTTP/2 server push from the browser engine. So please suggest optimization that do not include server push.</p>