|
|
|
|
|
by mcfunley
3413 days ago
|
|
Ok, I'll give you a serious answer. For an individual shipping a website, anything at all works. I'd guess that half of all websites that have existed are just a single person editing files directly on a webserver without source control, and that's fine. It's another matter altogether to ship code with tens of thousands of requests per second and a lot of teammates trying to change it simultaneously. |
|
Define "request"
If the "request" is to deliver some static file, that has been solved many years ago with CDNs and server caches and so on.
If the "request" is to do something other than static files, it has nothing to do with Web. It could be request to your bank's COBOL app or a request to their Java app or to their Node.js app. Nothing to do with Web.