In organizations all over the world, sustainability has become a watchword. This may be especially true in the public sector, as governmental and civil sector agencies are often tasked with the responsibility for implementing, overseeing and policing society’s sustainability initiatives. For as much political talk as exists around “government waste”, public sector entities have led the way in introducing sustainable policies, actively seeking ways to be better “green citizens”. Having a duty of care as a steward of the public good, and a responsibility to meet sustainability objectives, public sector agencies, big and small, have made strides in reducing energy consumption, introducing recycling initiatives, implementing green procurement programs and requirements, and so forth.
In a recent webinar, we shared some of the big dos and don’ts of Varnish use. After outlining the don’ts in an earlier blog post, we promised to follow up with a rundown of the five Varnish dos as presented in the webinar. Obviously, you should watch the webinar to get the full story on why and how you should take these actions in Varnish, but here’s a quick taster to give you a preview of what you’ll learn.
The single most frequent question I get from people discovering Varnish is "Do you support request collapsing?". And I must admit, it always catches me off guard, because of course, it has been doing so for years, and it's a caching server, so that's a must-have, right? (Yes, yes it is.)
For this reason, in this post, we are going to review some of the little features we take for granted but that also make Varnish a great origin shield.
For many years, we’ve fielded questions about which is better, Varnish or NGINX? We’ve always affirmed that both are great but for very different things. They aren’t identical solutions and don’t do identical things. And sometimes, they can be used in complementary ways to get the most from both.