Scaling Next.js App (expecting 20M visits/month)
Unanswered
Broad-snouted Caiman posted this in #help-forum
Broad-snouted CaimanOP
Hi everyone,
We are building a Next.js application utilizing server actions is anticipating a significant traffic increase, from 5 million to 20 million monthly visits. With a logged-in user base, each page load triggers at least one (often more) server-side action.
While scaling with additional servers can address basic needs, it's crucial to identify potential bottlenecks. We're seeking insights on:
1. Known issues encountered when using Next.js app router and server actions at this scale.
2. Performance optimization strategies, such as leveraging Redis for efficient caching on the server.
3. Real-world examples: Have any community members deployed similar-sized applications using Next.js app router and server actions? We'd be interested in:
- Their traffic volume
- Server architecture (e.g., instance types, number of servers)
- Average response times (focus on TTFB)
Thanks in advance for sharing your expertise!
We are building a Next.js application utilizing server actions is anticipating a significant traffic increase, from 5 million to 20 million monthly visits. With a logged-in user base, each page load triggers at least one (often more) server-side action.
While scaling with additional servers can address basic needs, it's crucial to identify potential bottlenecks. We're seeking insights on:
1. Known issues encountered when using Next.js app router and server actions at this scale.
2. Performance optimization strategies, such as leveraging Redis for efficient caching on the server.
3. Real-world examples: Have any community members deployed similar-sized applications using Next.js app router and server actions? We'd be interested in:
- Their traffic volume
- Server architecture (e.g., instance types, number of servers)
- Average response times (focus on TTFB)
Thanks in advance for sharing your expertise!