NGINX, the company behind one of the most popular web servers, has been acquired by F5. Of course, I’m glad for the NGINX team and founders, for who this is quite an accomplishment. But at the same time, much like many of the recent acquisitions, this one worries me. NGINX and F5 were competing in certain areas. That competition is now gone.
As always, they say that they will keep NGINX brand, team, technology, and even invest more in the Open Source side of things. But I’m not holding my breath. We’ve seen way too many screw ups on that front in the last few years.
Having the Open Source offering is good though. If it continues to grow and develop – even better. But if not, at least there is an option of forking, rebranding, and building on top.
Server Push was one of the most exciting features for me in all of the HTTP/2 specification. But I wasn’t quite sure how it will be implemented, and, most importantly, how it can be made easily available to the web developers, who are often few levels removed from the web server configuration. I think Nginx solves the problem quite elegantly.
On the configuration level, “location” directives are often available to the web developers withing the virtual host / server. But for those who can’t use those or don’t want to mess around with the configuration files, an even easier option is available – Link HTTP header.
I’m sure this will soon be widely supported in all the major libraries and frameworks, much like HTTP cookies are. Great times ahead!
Here are a whole lot of “Performance Tuning – Tips & Tricks” directly from the Nginx team. I’m sure you’ve seen bits and pieces of these all over the place, but it’s nice to have them all together and from the credible source as well.