6 ms·

After running Next.js in production for a few years I never want to touch it again. I haven't used Vercel, but hosting on AWS I had to patch configurations in d

After running Next.js in production for a few years I never want to touch it again. I haven't used Vercel, but hosting on AWS I had to patch configurations in dirty ways just to get it to run reliably. I suspect they "locked" things like node config behind the abstraction of Next.js to drive users to their platform where issues are "magically" solved.

c-hendricks 3y ago
Counterpoint, we deployed our first nextjs app on AWS last year and it's been very set-and-forget. Even with our hacky https in front of nextjs.
- shitlord 3y ago
  Are you using server side rendering? If so, did you end up writing a custom server, or are you monitoring your website some other way? My team is developing a server-rendered nextjs app which is deployed on AWS. We haven't really configured it beyond the defaults, but nextjs seems to provide very little visibility into what's happening (e.g., no request logs). If you could share any tips or lessons learned from operating a production nextjs app, it would be much appreciated.
  - cbovis 3y ago
    Have you considered NextJS middleware to decorate with request logging? https://nextjs.org/docs/pages/building-your-application/routing/middleware https://nextjs.org/docs/pages/building-your-application/rout...
    - shitlord 3y ago
      Thanks, that is helpful. The OpenTelemetry integration seems like it will provide the most useful insights.
    - willcipriano 3y ago
      Your load balancer/http server should have the request logs, are you running it bare?