4 ms·
this reminds me of stackoverflow's vertical scaling with a fail over server. drastically simplifies scaling when you are dealing with only one machine with hug
by pkkkzip 2y ago
this reminds me of stackoverflow's vertical scaling with a fail over server.
drastically simplifies scaling when you are dealing with only one machine with huge amount of RAM and maximum cores.
I think the most you can get now is 192x2 cores and double digit TB of RAM
but more economical is proably 128x2 cores with single digit TB of RAM
its pretty insane how much traffic you can throw at a single machine like this espeically if you use optimized languages like Go or Rust to handle traffic.
there's still use for distributed computing but 99.8% of websites do not really need it.
- a012 2y agoThis is what we did for a now defunct service where it’s scaled to a biggest available machine at that time (less than a TB of memory) and the db was mostly for a freaking giant table.