138: Tom Preston-Werner - Building Full-Stack JS Apps with Redwood.js
Episode
73 min
Read time
2 min
Topics
Remote Work, Relationships, Startups
AI-Generated Summary
Key Takeaways
- ✓Router Architecture: Redwood uses a single flat routing file instead of nested routing, making it simple to trace URLs to page components. All routes live in one place for easier debugging and long-term maintenance, though this requires solving layout persistence challenges with technical solutions under the hood.
- ✓Cells Pattern: Cells provide declarative data fetching by exporting query, success, failure, and empty state components. This abstraction allows Redwood to transparently solve problems like the GraphQL waterfall issue where nested components wait unnecessarily for parent queries to complete before fetching their own data in parallel.
- ✓Services Layer: Services sit above GraphQL resolvers as the primary back-end API, organizing business logic by domain (billing, content, accounts) rather than database tables. Functions export directly from service files, enabling reuse across services without resolver boilerplate while maintaining clear boundaries and encapsulation for maintainability.
- ✓Serverless Database Strategy: Redwood deploys GraphQL APIs as single Lambda functions, accepting current connection pooling limitations. The roadmap targets distributed databases like Yugabyte or Fauna for edge-ready deployments, with AWS RDS Proxy and Netlify partnerships addressing near-term scaling needs without requiring Kubernetes or server management.
- ✓Tutorial-Driven Development: Redwood's development methodology writes comprehensive tutorials first, then builds features to make tutorials work. This ensures the framework delivers the intended developer experience from day one, with the tutorial serving as the primary introduction and validation of core functionality for new users.
What It Covers
Tom Preston-Werner introduces Redwood.js, a full-stack JavaScript framework designed as a Rails replacement that deploys serverless, uses GraphQL APIs, React front-ends, and Prisma for database access with strong opinions on maintainability.
Key Questions Answered
- •Router Architecture: Redwood uses a single flat routing file instead of nested routing, making it simple to trace URLs to page components. All routes live in one place for easier debugging and long-term maintenance, though this requires solving layout persistence challenges with technical solutions under the hood.
- •Cells Pattern: Cells provide declarative data fetching by exporting query, success, failure, and empty state components. This abstraction allows Redwood to transparently solve problems like the GraphQL waterfall issue where nested components wait unnecessarily for parent queries to complete before fetching their own data in parallel.
- •Services Layer: Services sit above GraphQL resolvers as the primary back-end API, organizing business logic by domain (billing, content, accounts) rather than database tables. Functions export directly from service files, enabling reuse across services without resolver boilerplate while maintaining clear boundaries and encapsulation for maintainability.
- •Serverless Database Strategy: Redwood deploys GraphQL APIs as single Lambda functions, accepting current connection pooling limitations. The roadmap targets distributed databases like Yugabyte or Fauna for edge-ready deployments, with AWS RDS Proxy and Netlify partnerships addressing near-term scaling needs without requiring Kubernetes or server management.
- •Tutorial-Driven Development: Redwood's development methodology writes comprehensive tutorials first, then builds features to make tutorials work. This ensures the framework delivers the intended developer experience from day one, with the tutorial serving as the primary introduction and validation of core functionality for new users.
Notable Moment
Preston-Werner reveals his frustration with JavaScript tooling led him to build Redwood after finding no suitable ORM until Prisma 2 emerged. He invested in Prisma after choosing it, believing their query builder finally matched Active Record's developer experience in the JavaScript ecosystem.
Episode Transcript
In this episode of Fullstack Radio, I talked to Tom Preston Werner about building full stack JavaScript applications with Redwood JS. This is Fullstack Radio episode one thirty eight. So the reason that I wanted to have you on the show is I don't know when this maybe a month ago, maybe not even a month ago. You and, the team that you've been working with recently announced Redwood JS, which from the outside looks like an attempt to to kind of build the full stack sort of Node. Js JavaScript driven framework that everyone's kind of been wanting for years. The thing that all the Rails developers have been complaining about that didn't exist in in node land. And from the looks of it, it looks like you've got sort of a pretty interesting take on it. So I'm really curious to learn sort of, more about Redwood JS. Absolutely. Yes. So Redwood JS is indeed an attempt to build a full stack framework for JavaScript and to really deploy it in a serverless way. So that's one of the the primary tenants that we have is build it end to end with JavaScript and deploy it to a serverless environment to give you the advantages of the scale that that can bring as well as the global distribution that that can bring. So one thing that we say about Redwood is that it's edge ready. And by that, we mean all of the different parts of redwood should be able to operate on the edge once technology plays out a little bit more. This is not entirely true today, but really we're building redwood today with an eye to the future. So Redwood is not yet fully realized, but the idea is that if we start today with the idea that some of these technologies will exist in the way that we want them to in, say, a year, then we'll be there when the technology is ready. Instead of the technology existing first and then coming in and saying, oh, let's take advantage of this, and then it takes another year or more to build for it. It's like the way that game programmers build their games for the hardware that will exist That doesn't yeah. When they release. Right? We're doing the same thing, but with web technology. So So placing some bets that, some of the tooling that you kind of need to kinda make this thing work, the way you you believe it has the potential to work are going to exist, you know, in the near ish future. Yeah. Absolutely. And so I I can dive into those just real quick to go over them. So as far as the edge readiness goes, so so the whole point of Redwood really is to take advantage of a Jamstack architecture. And so you start with the client, which ends up being a React based, JavaScript, client that can be delivered statically. So So I …
Get the full transcript (14,179 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 70-minute episode.
Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from Full Stack Radio
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
Aug 21 · 76 min
Syntax
986: Does Code Quality Matter Anymore?
Mar 11
More from Full Stack Radio
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
Jan 28 · 47 min
The Changelog
A new direction for AI developer tooling (Friends)
Oct 10
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
“Tom Preston-Werner introduces Redwood.js, a full-stack JavaScript framework designed as a Rails replacement that deploys serverless, uses GraphQL APIs, React front-ends, and Prisma for database access with strong opinions on maintainability.”
“The roadmap targets distributed databases like Yugabyte or Fauna for edge-ready deployments, with AWS RDS Proxy and Netlify partnerships addressing near-term scaling needs.”
“Tom Preston-Werner introduces Redwood.js, a full-stack JavaScript framework designed as a Rails replacement that deploys serverless, uses GraphQL APIs, React front-ends, and Prisma for database access.”
by Amazon Web Services
“The roadmap targets distributed databases like Yugabyte or Fauna for edge-ready deployments, with AWS RDS Proxy and Netlify partnerships addressing near-term scaling needs.”
- PrismaRecommended
“Preston-Werner reveals his frustration with JavaScript tooling led him to build Redwood after finding no suitable ORM until Prisma 2 emerged. He invested in Prisma after choosing it, believing their query builder finally matched Active Record's developer experience in the JavaScript ecosystem.”
“Tom Preston-Werner introduces Redwood.js, a full-stack JavaScript framework designed as a Rails replacement that deploys serverless, uses GraphQL APIs, React front-ends, and Prisma for database access.”
“The roadmap targets distributed databases like Yugabyte or Fauna for edge-ready deployments, with AWS RDS Proxy and Netlify partnerships addressing near-term scaling needs.”
company
“The roadmap targets distributed databases like Yugabyte or Fauna for edge-ready deployments, with AWS RDS Proxy and Netlify partnerships addressing near-term scaling needs.”
More from Full Stack Radio
We summarize every new episode. Want them in your inbox?
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
151: DHH – Building HEY with Hotwire
150: Secret Screencasting Tips & Behind the Scenes of Tailwind CSS 2.0
149: Choosing a Payment Processor, Radical Icons & W3C Hype
Similar Episodes
Related episodes from other podcasts
Syntax
Mar 11
986: Does Code Quality Matter Anymore?
The Changelog
Oct 10
A new direction for AI developer tooling (Friends)
Shop Talk Show
Jun 16
669: Peter Pistorius on Developing RedwoodSDK
10% Happier with Dan Harris
Aug 17
You Can Get Through It: How to Handle the Hardest Things That Will Ever Happen to You | Dr. Lucy Hone
Dwarkesh Podcast
Aug 11
Ryan Greenblatt – Human level AIs might build runaway superintelligences by 2032
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into Full Stack Radio.
Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime