902: Fullstack Cloudflare with React and Vite (Redwood SDK)
Digest
This podcast introduces Redwood SDK, a React framework built for Cloudflare, emphasizing its speed, affordability, and ease of use. Creator Peter explains its core features: leveraging Cloudflare's edge network for server-side rendering, React server components, and real-time capabilities via durable objects. He highlights the cost-effectiveness and global reach of the Cloudflare platform. The discussion contrasts Redwood SDK's transparent design, avoiding "magic" and hidden abstractions, with other frameworks like RedwoodJS (now Redwood GraphQL) and NextJS. Key advantages of Redwood SDK include its Vite integration and direct access to Cloudflare services. Limitations are discussed, primarily the inherent reliance on Cloudflare's infrastructure. Finally, Peter shares his vision for Redwood SDK's future, including its potential integration with AI agents and its role in empowering individuals to build software more easily and affordably. The podcast also touches upon routing, noting that while a built-in client-side router isn't included, developers have flexibility to integrate their preferred solution.
Outlines

Introduction to Redwood SDK and Core Features
The podcast introduces Redwood SDK, a new React framework built for Cloudflare, focusing on speed, affordability, and ease of use. Peter, the creator, explains its core functionality: a React framework leveraging Cloudflare's edge network, server-side rendering, React server components, and real-time capabilities via durable objects. He emphasizes the cost-effectiveness and global reach of the Cloudflare platform.

Design Philosophy, Developer Experience, and Framework Comparisons
Peter discusses Redwood SDK's transparent design, avoiding hidden abstractions, and contrasts this with RedwoodJS and other frameworks like NextJS. The conversation highlights Redwood SDK's unique advantages in terms of server components, Vite integration, and direct access to Cloudflare services, while also addressing limitations related to its reliance on Cloudflare's infrastructure.

Redwood SDK's Future and AI Integration
Peter shares his vision for Redwood SDK's future, emphasizing its role in empowering individuals to build software easily and affordably, particularly with the rise of generative AI. The integration with AI agents and future development plans are discussed. The podcast also clarifies the relationship between Redwood SDK and the original RedwoodJS (now Redwood GraphQL). Finally, it addresses routing, explaining that while a built-in client-side router isn't provided, developers have the flexibility to integrate their preferred solution.
Keywords
Redwood SDK
A React framework built for Cloudflare's Workers platform, offering server-side rendering, React server components, and real-time capabilities with a focus on simplicity and developer experience.
Cloudflare Workers
Cloudflare's serverless compute platform, enabling developers to run JavaScript code globally at the edge of the network.
React Server Components (RSC)
A feature in React that allows rendering parts of a React application on the server, improving performance.
Durable Objects
A stateful object storage system within Cloudflare Workers, crucial for building real-time applications.
Vite
A fast build tool for JavaScript applications, integrated into Redwood SDK.
NextJS
A popular React framework often compared to Redwood SDK.
Serverless
An execution model where the cloud provider dynamically manages the allocation of computing resources.
React Framework
A JavaScript library for building user interfaces.
Q&A
What are the key advantages of using Redwood SDK over other React frameworks?
Redwood SDK offers a streamlined developer experience with direct access to Cloudflare's infrastructure (edge network, durable objects, D1 database), resulting in faster performance, lower costs, and easier deployment. It prioritizes transparency and avoids unnecessary abstractions.
How does Redwood SDK handle real-time updates?
Redwood SDK leverages Cloudflare's durable objects and integrates seamlessly with React Server Components. Updates from server actions are automatically broadcast to all connected clients.
What is the relationship between Redwood SDK and the original RedwoodJS?
RedwoodJS has been renamed Redwood GraphQL and is being unbundled. Redwood SDK represents a new direction, focusing on a simpler, more integrated approach with Cloudflare.
What are some of the limitations of using Redwood SDK?
Applications built with Redwood SDK are inherently tied to the Cloudflare platform. There might be minor incompatibilities with certain packages.
How does Redwood SDK handle routing?
Redwood SDK doesn't include a built-in client-side router; developers can integrate their preferred solution.
Show Notes
Wes talks with Peter Pistorius about RedwoodSDK, a new React framework built natively for Cloudflare. They dive into real-time React, server components, zero-cost infrastructure, and why RedwoodSDK empowers developers to ship faster with fewer tradeoffs and more control.
Show Notes- 00:00 ">00:00 Welcome to Syntax!
- 00:52 ">00:52 What is RedwoodSDK?
- 04:49 ">04:49 Choosing openness over abstraction
- 08:46 ">08:46 More setup, more control
- 12:20 ">12:20 Why RedwoodSDK only runs on Cloudflare
- 14:25 ">14:25 What the database setup looks like
- 16:15 ">16:15 Durable Objects explained – Ep 879: Fullstack Cloudflare
- 18:14 ">18:14 Middleware and request flow
- 23:14 ">23:14 No built-in client-side router?
- 24:07 ">24:07 Integrating routers with defineApp
- 26:04 ">26:04 React Server Components and real-time updates
- 29:53 ">29:53 What happened to RedwoodJS?
- 31:14 ">31:14 Why do opinionated frameworks struggle to catch on?
- 34:35 ">34:35 The problem with Lambdas
- 36:16 ">36:16 Cloudflare’s JavaScript runtime compatibility
- 40:04 ">40:04 Brought to you by Sentry.io
- 41:44 ">41:44 The vision behind RedwoodSDK
Syntax: X Instagram Tiktok LinkedIn Threads
Wes: X Instagram Tiktok LinkedIn Threads
























