4 ms·
I helped stand up Notion’s marketing site (https://notion.so/product https://notion.so/product) on NextJS. It’s really annoying / impossible to implement all t
by jitl 3y ago
I helped stand up Notion’s marketing site (https://notion.so/product https://notion.so/product) on NextJS.
It’s really annoying / impossible to implement all the fancy caching, incremental revalidation, etc if you need to run more than one instance to serve the load you get. Or you need a horrendously complex AWS buzzword graph that will kinda sorta do the things. We switched from AWS ECS deployment to Vercel after tiring of figuring out how to support Next features that require very tight cooperation from CDN/distributed cache magicks.
The total product is good, the web presence team is happy with Next and Vercel, I’m liking RSC and server actions, but I wanted to share my experience that beyond modest scale running Next yourself needs a lot of effort.
- ushakov 3y agoCurious whether you considered any other frameworks?
- jitl 3y agoSite predates Astro, Remix, etc. There was some interest in Gatsby but I said no (seems horribly over engineered, adds GraphQL for no good reason, like storybook promises a lot but seems to leave the team doing extreme amount of npm upgrade work). I think Next was the clear winner, we knew what we were getting into with hosting it to some degree and it was still worth because of how well it fits the team.
- satvikpendem 3y ago> We switched from AWS ECS deployment to Vercel after tiring of figuring out how to support Next features that require very tight cooperation from CDN/distributed cache magicks. I guess that's how they get you, by making it onerous to self host and instead offering a clean yet more expensive solution.