I'm looking to set up a web server primarily for redirecting users to specific files. For example, if someone goes to `https://example.com/id1`, they should be redirected to `https://example.com/id1/filename1.html`. These `filename1.html` files are going to be cached aggressively, and while hits may be occasional, I don't want the server to serve them directly every time since they don't change often, but they might be replaced with new files. I need the server to handle dynamic redirection to the currently available file in a folder, and I'm currently using PHP. I'm curious which web server, like Apache or Nginx, would perform best for this kind of setup where most traffic will go through these redirects.
4 Answers
If you're dealing with low traffic, sticking with Apache and PHP should be fine. But if you're handling between 100 to 1,000 requests per second, I’d say switch to Nginx. It works really well with static maps for redirects and can easily handle loads of up to 10,000 requests per second on a single setup. For heavier traffic, consider using Nginx with Redis to scale across multiple servers effectively.
Exactly, you would normally need to update the map. You can automate this process with scripts, but if you expect constant changes, keep that in mind!
Using Nginx with caching can really up your performance. Configure it to cache PHP responses temporarily so that you’re not hitting the filesystem every time. This way, you can serve thousands of requests per second while only calling PHP once every few seconds for updates.
You might want to consider OpenLiteSpeed, as it's optimized for handling static content and performs well with lightweight setups. It could also seamlessly manage your redirects with less overhead than traditional servers.
For this use case, I suggest looking into a serverless solution like Cloudflare R2. It’s set up for static file storage, and it minimizes overhead. Plus, there are no bandwidth costs to worry about, which makes it very appealing for high traffic scenarios.
Interesting! How would it handle the redirection when I have to point to specific files based on the folder? Does it allow for that kind of dynamic handling?
Yes, you can set up edge functions or workers to manage those redirects dynamically, it's quite flexible!
Thanks for the tip! I’ve never used static map files before. Do I have to manually rebuild the map and reload Nginx every time I add a new file? That seems tricky, especially if files get updated often.