Ticket to Ride

HTTP/2 Early Hints

HTTP/2 is becoming increasingly widespread, as a consequence of which the demand for the push feature is also growing in the Rails community. Unlike HTTP/1.1, where a web client can only fetch files from the web server using HTTP GET, HTTP/2 also allows the web server to deliver unsolicited files actively to the web browser, which also increases the web performance of a web application.

Rails Core member Aaron Patterson has incorporated HTTP/2 into the new Rails version with the help of Eileen Uchitelle so that the web server above the Rails layer is tasked by the Rails framework with pushing stylesheets and JavaScript assets to the web browser.

This area is likely to see a lot of movement in future Rails versions. Thus far, Rails asset management is still building on the basic idea for HTTP/1.1 of sending one large file, rather than many small files that HTTP/2 can send.

Redis Cache Store

The new Redis Cache Store also comes from the Basecamp lab. With the new gem, Jeremy Daer has created a very stable and fast way to address Redis as a cache in distributed mode, which allows data to be stored on different Redis servers.

Those who rely on the Russian matryoshka doll strategy for fragment caching can look forward to an improved cache lifetime by default, and without additional work thanks to key recycling and compression.

Conclusions

Ruby on Rails 5.2 is a minor update and should integrate easily into existing Rails applications. The new version is not a revolution, but a handy set of solid improvements. Active Storage is likely to be the biggest change and optimization for most Rails users. Also on the horizon is Ruby 2.6, which is in a preview release (see the "Ruby 2.6" boxout).