Next.js is a backend framework
summary
Claim: Next.js functions as a backend framework, not just a React renderer, and that claim is shown by concrete features and tradeoffs. It uses getServerSideProps and getStaticProps to emit HTML, exposes real request/response handlers via \/pages\/api, and surfaces middleware and edge redirects. React’s async server component RFC effectively makes React backend-capable. Serverless lambdas dying after response force design changes for background work; practical fixes include Pusher, Liveblocks, Ably, Zeplo, Upstash and S3 presigned URLs for uploads.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:30Backend vs frontend
- 1:55Full-stack spectrum
- 4:05React's backend-first
- 5:08Next.js full-stack
- 6:54Serverless limits
- 8:19Serverless-ready tasks
- 9:40Backend challenges solutions
- 10:46Why Next.js bridges them
- 11:06Closing remarks
related talks
39mKeynote on Next.js and Serverless future
22mNext.js is my main web server for all APIs. And I like it!
45mNext.js: How Do You Even Render?
28mMastering Server-Side Development for React Developers
15mBuilding Isomorphic JavaScript Apps Faster with Next.js
40mServer-Side Rendering 2.0? React Server Components
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
33mServer Components are React's superweapon in the Stack Wars