Yes, one machine is all you need in most cases if you really think about it. If you need more it will be pretty obvious. Then you should absolutely setup more machines.
Then there is managed services route, where you don't even know where exactly you are deploying stuff and use Vercel, Supabase, Serverless of some kind etc. This is also valid, but then you relay on 3rd parties and their lava lamps.
I mean if the 2% of the whole internet does not have JS, and they are not a part of your target demographics, then it's not a problem in a business sense. If they are, then yup, you should be prepared.
This post is great in terms of making you aware that even in near perfect conditions JS might be not available, but the impact and solutions should be considered on a case-by-case basis.
Yes, one machine is all you need in most cases if you really think about it. If you need more it will be pretty obvious. Then you should absolutely setup more machines.
Then there is managed services route, where you don't even know where exactly you are deploying stuff and use Vercel, Supabase, Serverless of some kind etc. This is also valid, but then you relay on 3rd parties and their lava lamps.