React Server Components (RSC) represent a powerful new paradigm for building fast, interactive web applications by allowing server-side rendering of components alongside client-side ones. While Next.js has emerged as a popular framework for leveraging RSC, it's not the only option.

In this talk, we'll explore how to integrate React Server Components into a custom application without relying on Next.js. You'll learn about the core concepts of RSC, the benefits of server-side rendering, and how to configure your own custom server environment to take full advantage of RSC in any React project. By the end, you'll walk away with a deep understanding of how React Server Components work independently of popular frameworks and how to apply them to improve performance and scalability in your applications.

A real-world deep dive into React Server Components (RSC) and server actions—what they enable, their challenges, and why debugging RSC payloads can be a nightmare. Expect an honest take on RSC’s strengths and limitations.

I’ve been building UI components with React for a while now, and I’ve read a lot about server-side rendering (SSR). From what I’ve read, I didn’t expect SSR to affect how React components are built.

Lately, I’ve been working on a component library, and one of the consumer teams I worked with uses SSR. After building many components, I received feedback that several of them weren’t working correctly when SSR was used. This got me thinking about why this was happening and how SSR might affect building React components.

Building a server driven UI with React is perfect as Reacts dynamic nature makes it easy to render and update UIs based on API responses but it still requires many round trips over the network. React 19 and RSCs are a perfect solution to this problem! By leveraging the new features in React 19 we can now build an even more performant server driven UI. In this talk I’ll demo how I’ve been able to leverage React 19 and RSCs in an enterprise application to build server driven UIs.