HTTP/2 is shipping in browsers and servers throughout 2016. The protocol brings multiplexing, server push, and binary framing—fundamental changes that supposedly invalidate HTTP/1.1 optimization practices like domain sharding and sprite sheets.
Reality is messier. Not all browsers support it. Not all servers either. And some HTTP/1.1 optimizations still help. The transition period is awkward.
Your web application is slow. Pages take seconds to load. Users are complaining. You check your code – it's fine. You check your server – plenty of resources. The problem? Your database queries.
Database performance is often the bottleneck in web applications. A poorly optimized query can turn a fast application into a sluggish mess. But with the right techniques, you can make your database scream.