Journal/Web Development

The Rise of React Server Components

React Server Components are changing how we think about building web applications. Here's what they mean for performance, developer experience, and the future of React.

Feature image for the-rise-of-react-server-components

A new mental model for React

React Server Components (RSCs) are the biggest shift in the React ecosystem since hooks. They render components on the server and send the resulting HTML plus minimal JavaScript to the client.

This isn't traditional SSR. RSCs are a hybrid model where some components run only on the server, others run on the client, and the two compose together cleanly.

Why this matters

Smaller bundles

Server Components don't ship their JavaScript to the browser. If a component only needs to fetch data and render HTML, the client never has to download or parse that code. Bundle sizes drop noticeably.

Direct backend access

Server Components can hit databases, file systems, and internal APIs directly, without standing up a separate API layer. Data fetching becomes simpler.

Streaming and suspense

RSCs work naturally with React's streaming. The server can send parts of the page as they're ready, instead of holding everything back until the slowest query returns.

The Next.js App Router

Next.js has driven RSC adoption through its App Router. Components in the App Router are Server Components by default. You opt into client-side interactivity with the 'use client' directive.

The server-by-default posture nudges developers to keep client-side JavaScript lean, which tends to produce better performance.

Practical implications

For the projects we build at CodeDrips, RSCs open up things that used to be a slog. CMS-driven sites benefit most because content fetching happens server-side with no client-side JavaScript overhead. eCommerce product pages can render on the server while cart interactions stay on the client. Data-heavy dashboards stream their content without blocking the whole page.

The learning curve

RSCs add complexity. Understanding the server-client boundary, knowing when to reach for 'use client', and managing serialisation between server and client components takes a shift in thinking.

The payoff in performance and user experience makes it worth the effort for most projects. As the ecosystem matures, the developer experience keeps improving.

Looking ahead

React Server Components are a new paradigm for building web applications. Paired with frameworks like Next.js and Gatsby, they show where React is heading. Atlassian and Canva, two Australian engineering shops with reach, have both leaned into server-rendered React for the same reasons. Understanding RSCs now puts you ahead of the curve.

Filed under: Web Development. Last edited 30 January 2026. Send corrections.
§ Read next
Server-Side Tagging on a Gatsby or Next.js Site: Why and How
/ Web Development
Server-Side Tagging on a Gatsby or Next.js Site: Why and How
HubSpot vs Customer.io vs Klaviyo: Picking a Marketing Automation Stack
/ Technology
HubSpot vs Customer.io vs Klaviyo: Picking a Marketing Automation Stack
§ Web Development services we offer

§ Subscribe

One letter,
once a month.

Studio essays, postmortems and the occasional Risograph print drop. No tracking pixels, no automation funnels.

hello@codedrips.com →