Avoid showing user specific information by wrongful caching
Usually guests see some bits different then logged in users. A simple way to start with Varnish is to avoid all the caching logic for logged in users.
Proper basic auth with Varnish Cache
Caching and everything else should work behind basic auth too.
Moving all non-essential config from Nginx to Varnish Cache
That way we define one single source of truth for all business logic related to incoming requests, caching, header transformation, etc...
Proper redirects handling
Handle as many redirects as possible outside of your application
Just block bad url requests in general
If you have a Laravel or Symfony or Ruby or Python or Next.js application, or some fancy flavor of a CMS, then why do you need to allow wordpress requests coming in?
How to avoid ugly peak traffic by blocking bots
There are good bots, and then there are the others. And they can cause some trouble with aggressive peaks in traffic.
How handling 404s well, after migrating from Magento 2 to Laravel, can save you money
You can either scale horizontally OR you can optimize your nginx config for handling of missing files.
