Alex RussellFriends, I am *wheezing*. People on this plane are giving me looks. Holy shit...like...hahahahahahaha....omg...doubled over laughing:
https://martijnhols.nl/blog/how-much-traffic-can-a-pre-rendered-nextjs-site-handle
benschwarz@slightlyoff Martin’s testing method is a little bit peculiar — was the issue really next.js? Or lack of load balancing and infrastructure right sized for the workload?
The article closes saying SSR isn’t appropriate for lots of traffic, but… doesn’t discuss caching, or if a page truly needs to be 100% dynamic.
There’s a lot of high traffic fully/semi dynamic pages out there, SSR is just fine for so many applications.
TLDR: next isn’t likely the problem here at all
PointlessOne 
To show that next is not a problem it’d be informative to benchmark a fully static site on the same server.
I mean, you can collect your own data to back your claim.
@pointlessone @slightlyoff My 'claim' isn't something even slightly unbelievable! Dynamic workloads have numerous levers to pull to eek out request performance.
Off the top of my head: Load balancing reverse proxies, employing a CDN, use well-suited cache headers, use server-side caching, use partial response caching, ensure the server has enough CPU/memory for the workload, ensure there's autoscaling, eliminating slow DB queries.
All of which will improve RPS for dynamic workloads.