Skip to content
0:00 / 0:00

#next.js#trpc#serverless

Do you REALLY need a backend?

Theo - t3․gg

576K subscribers • 14 videos on Hallway

YouTube
  • Recommended by 3 people: 3 in engineering communities.
  • Presented by Theo Browne, creator of t3.gg
  • May be out of date. The tools, versions or practices it shows have likely moved on.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

140K views4 years ago3 recommendations

Web developmentSoftware designVue, Svelte, Angular and othersFull-stack frameworksSoftware architecture

Theo Browne argues that Next.js functions as a complete backend framework, making separate backend services unnecessary for many applications.

It's time for a narrative change. NextJS is a backend framework, even if it includes React. Long overdue rant. Sorry for all the individuals I call out during this one, no hard feelings to y'all. s/o Idez for keeping the damn channel alive while I was traveling. Back Wednesday!!! Timestamps: the tweet explanation time next endpoint example trpc example “next api’s are too much work” auth summary outro

Why it's here

3 people recommend this

What people say. Recommended for its perspective on using Next.js as a full-stack framework to reduce architectural overhead.

u/Anbaraenin r/node • Recommends

On “Which back-end should I use for my Next.js project?”

NextJS. See Theo's video for why. You do not need another backend, you're adding unnecessary overhead.

u/Xzas22in r/node • Recommends

On “Which back-end should I use for my Next.js project?”

Next, especially now with 12.2 edge functions being so insanely powerful, is a full stack framework. link to this video

u/RJCPin r/node • Recommends

On “Moving from Ruby On Rails to Node.js”

…u’ll have the best developer experience building some stuff with that with Prisma, react-query and a couple other packages It’s easy to deploy serverless, and it halves the amount of work you’d need to do if you want to build independent front ends and backends. Theo made a pretty decent rant on this a couple of months ago for some perspective: link to this video I strongly disagree with his views on NestJS however, the structure is great. He comes from a privileged background of having worked mostly with high quality devs in a FAANG environment, and hasn’t seen the extent to which, for example, inexperienced devs or people with broken English can make a complete shitshow mess of an express app. Ha…

u/carlpaul153in r/node • Mentions

On “Libraries and frameworks to use JS in the backend. Did I understand correctly? Also, where would Nextjs and Remix go?”

Hello everyone. There are so many technologies that can make those of us just starting out dizzy. I hope someone can find this map as helpful as it was for me. Please if you see any errors let me know. Regarding Nextjs, I know you can remove the API folder and use whatever backend you prefer. But, how would this affect the functionalities of SSR, SSG, etc? Is the API folder based on express? I've read that in a couple of comments but I can't find an official basis. Similar doubts apply to Remix. Apparently, I'm not the only noob who has difficulty understanding the role of Nextjs or Remix in the backend. This video seems a clear example of it.