Post

my humble opinion is that if people took the time to understand react server components, they would see that 90% of websites would net benefit from their architecture. you only have to learn how they work once. most of the cost is cognitive, not architectural.

IME this is not the case unless you can afford to offload architectural thinking to Vercel or don’t really have much traffic to handle.

I actually prefer self hosting it. It’s not that difficult. A docker container and Cloudflare fronting your server gets you most of the way there.

Yeah if you can heavily cache most requests you can keep server load minimal. Ive found it difficult to manage performance, even behind a CDN, when some or all routes require a server round trip. Getting consistent request latency requires a lot more containers available to serve requests.

That’s not to say deployment has no complexity. It definitely adds overhead.

Bingo! Literally fighting this right now. Replace DB with microservices which each may hit their own DB or cache + getting the observability needed to understand where the time is going in each request and it can be rather joy-sucking work.

Are you using OTEL traces? I actually built an entire observability platform to solve this problem (was planing to ship it commercially but got sidetracked into this as it’s more up my alley). I still use that platform for my needs.