Understanding React Server Component

Introduction

As most of us already know, React enables us to break down interfaces into independent parts called Components, facilitating reuse and customization. Currently, React Components are divided into two main types:

  • Client Components: widely used in Client Side Rendering (CSR) applications.
  • Server Components: a new type of component that renders on the server side before being sent to the client (browser). At first glance, it may seem similar to Server Side Rendering (SSR) which has been used for a while, but in reality, these two concepts have certain differences.

The Difference of RSC (React Server Component)

  1. Ease of development: React Server Component allows easy direct connection to server-side resources such as databases or internal services, streamlining development processes.
  2. Improved performance: By reducing latency in communication between client and server, React Server Component enhances overall application performance.
  3. Reduced source code size: Libraries utilized only on the server side need not be transmitted to the client, resulting in a lighter source code footprint.
  4. Additionally, Server Components automatically split the source code into smaller parts, allowing clients to load only necessary sections, thus optimizing performance. This means we no longer need to use techniques like lazy loading as previously required.
const Component = React.lazy(() => import('./component'))


Just import the components directly that we need to use:

import Component from './server-component'


Comparing Server Side Rendering with React Server Component

  • In both Server Side Rendering (SSR) and Server Component, rendering occurs on the server side. However, Server Side Rendering only returns raw HTML upon initial page load. On the other hand, Server Component is treated as an actual component, meaning we can define multiple Server Components, use them in various places, and reuse them multiple times.
  • With Server Component, the result received from the server is merged with the current interface by React to create a new interface.

Limitations of Server Component

  • Since Server Component is created on the server side, it cannot be used with web browser APIs like accessing window or document variables.
  • Also, React APIs such as useState, useContext, useEffect, etc., cannot be used, resulting in Server Component not supporting user-interactable events in the application.

Example Usage

Here's a simple example using Server Component to load data, simultaneously with Client Component. Note that we'll use Next, and the example will be defined in the app directory.

First, create a file app/demo/Todo.tsx.

import {ResTodo} from './type'

// React Server Components
export default function Index({data}: {data: ResTodo}) {
return (
<div>
<ol className="pl-10 list-decimal">
{data.todos.map(todo => (
<li key={todo.id}>{todo.todo}</li>
))}
</ol>
</div>
)
}

Next, create a file app/demo/AddTodo.tsx.

'use client'

import {useState} from 'react'
import {addTodo} from './service'

// Client Components
export default function Index() {
const onAddTodo = (): void => {
addTodo({todo})
}
return (
<div>
<Input placeholder="Todo title" onChange={}></Input>
<Button onClick={onAddTodo}>Add</Button>
</div>
)
}

Finally, create a file app/demo/page.tsx, where the getTodoData function is used to directly fetch the todo list from the server. We can query the database to fetch the data right here.

import {getTodoData} from './service'
import AddTodo from './AddTodo'
import Todos from './Todos'

// React Server Components
export default async function Index() {
const data = await getTodoData()
return (
<div>
<AddTodo />
<Todos data={data} />
</div>
)
}

When you successfully start the application, in the Sources tab, you'll only see the AddTodo.tsx file (Client Component) in the client-side source code, without the Todo.tsx file (Server Component).

Bundle response of client side

In Summary

  • React Server Component is a new feature supported by Next from version 13, currently still in development and testing phase. You should consider carefully if you want to use it in a production environment.
  • However, once the feature becomes stable, it promises to be a significant development step for React, providing better support for SSR and optimizing React applications further.
If you have any suggestions or questions regarding the content of the article, please don't hesitate to leave a comment below!

Comments

Post a Comment

Popular posts from this blog

A Handy Guide to Using Dynamic Import in JavaScript

Image
Introduction In JavaScript, when we import a file, the process usually happens synchronously, known as static import. However, as our applications grow, this synchronous loading can lead to slower initial page loads due to larger JavaScript bundles. Moreover, there are times when imports are necessary only under specific circumstances, leading to unnecessary loading times for users who might not even utilize those features. Details Instead of burdening all users with unnecessary imports, dynamic imports come to the rescue. They allow us to load modules or files only when they are needed, thus improving performance and user experience. Dynamic imports are invoked using the import() function and return a promise. When using default exports, the exported data can be accessed through the default field, while other data can be accessed through fields with matching names. Here's how you can use dynamic imports: import ( "ramda" ). then ( module => { const moduleDefaul
Read more

What is react-query? Why should we use react-query?

Image
Introduction You might have heard or seen others mention the react-query library quite often. Why should we use react-query when we can use useEffect to fetch data from an API ? This article will answer that question. What is react-query? react-query is a set of hooks for fetching, caching, and updating asynchronous data in React . Simply put, react-query is a library for fetching , caching , and updating asynchronous data when used in React . Why should we use react-query? Normally, there are many ways to fetch data from a server. Some popular methods include using useEffect and useState , or using a state management library like redux . export const Page = () => { const [ data , setData ] = useState (); useEffect (() => { const loadData = async () => { const response = await fetch ( hostAPI ). then ( response => response . json ()); setData ( response ) } loadData () }) return < DisplayData /> } This me
Read more

Explaining Async/Await in JavaScript in 10 Minutes

Image
Introduction For a long time, we've relied on callbacks to deal with asynchronous code in JavaScript. As a result, many of us have faced dreadful experiences dealing with deeply nested functions ( callback hell ). Callback hell Callbacks come with a lot of drawbacks. When we have multiple asynchronous operations, callbacks have to wait for each other to execute, prolonging the completion time. Additionally, writing nested callbacks makes our code messy and hard to maintain. In the ES6 (ECMAScript 2015) version, JavaScript introduced Promises. This was a fantastic replacement for callbacks and was quickly embraced by the community. Our new code looks similar to the old one, making it easier to follow and maintain. However, the issues with callbacks weren't completely resolved. Since the ES7 (ECMAScript 2016) version, Async/Await has been added to make asynchronous code in JavaScript look and feel easier to use. What is Async/Await? Async/Await is a feature of JavaScript that
Read more

Using styled-components in React/Next Applications

Image
Introduction When it comes to styling your React application with a css-in-js approach, styled-components stands out as a top choice. In this post, I'll walk you through how to utilize styled-components in a Next application. By default, Next provides a way to use  css-in-js  through styled-jsx. However, if you find styled-jsx cumbersome because it requires writing CSS within JSX , which can make your components lengthier, then styled-components might be the right fit for you. Installation of styled-components npm install styled-components // or yarn add styled-components Example usage: import styled from 'styled-components' const Wrapper = styled . div ` color: red; text-align: center; ` // Component with input param const Wrapper2 = styled . div <{ $color ?: string }> ` color: ${ props => props . $color } ; text-align: center; ` export default function Index () { return ( <> < Wrapper > Demo 1 </ Wrapper >
Read more

Enhance Security for Node.js Applications

Image
1. Limiting the number of requests Limiting the number of requests (from a single IP address within a specific timeframe) is a method used to prevent denial-of-service (DOS, DDOS) attacks or brute force attacks that could overload your server. If you're using Express, integrating this is quite straightforward using the express-rate-limit  package. import * as express from 'express' import helmet from 'helmet' import expressRateLimit from 'express-rate-limit' const app = express () const limiter = expressRateLimit ({ windowMs: 10 * 60 * 1000 , // ms, ~10 minutes max: 50 , // limit each IP to 50 requests }) const specificLimiter = expressRateLimit ({ windowMs: 60 * 60 * 1000 , // 1 hour window max: 2 , // start blocking after 2 requests message: 'Too many requests' , // default 429 TOO MANY REQUESTS }) app . use ( limiter ) // use for all route . use ( '/common' , ( req , res ) => { res . json ({
Read more

Constants, Object.freeze, Object.seal and Immutable in JavaScript

Image
Introduction In this article, we're diving into Immutable and Mutable in JavaScript, while also exploring how functions like Object.freeze() and Object.seal() relate to Immutable . This is a pretty important topic that can be super helpful in projects with complex codebase. So, what's Immutable? Immutable is like a property of data in JavaScript. It means once the data is created, it can't be changed. This allows for better memory management and catching changes promptly. This is a big deal and totally contrasts with Mutable, which is the default nature when you initialize data in JavaScript. Implementing Immutable in a project makes development much smoother, reduces issues that crop up, and saves a ton of effort and time for maintenance down the road. But what happens if you don't use Immutable? Let me give you an example of how changing data during development can lead to some serious issues. let info = { name: "name" , address: "addres
Read more

Installing PostgreSQL with Docker

Image
Introduction In this guide, I'm going to walk you through installing PostgreSQL database and pgAdmin using Docker. The big advantage here is it's quick and straightforward. You won't need to go through a long manual installation process (and potentially spend time fixing errors if they arise). Installing Docker If you don't already have Docker installed on your machine, you'll need to do that first. At this step, you'll need to search Google because the installation process depends on the operating system you're using. Typically, installing Docker on Windows is simpler compared to using Ubuntu . Installing PostgreSQL Once Docker is set up, the next step is to install the PostgreSQL image. Here, I'm using postgres:alpine , which is a minimal version of PostgreSQL (it's lightweight and includes all the essential components needed to use PostgreSQL). docker run -- name postgresql - e POSTGRES_USER ={ username } - e POSTGRES_PASSWORD ={ passwor
Read more

Sitemap

Image
A page aggregator designed for easy reference and search, compiling all blog posts for convenient access.
Read more

Using PureComponent and React.memo to Improve Performance in React

Image
Introduction PureComponent in React is built on the concept of Pure Function. In this article, let's dive into PureComponent and the memo hook in React, as well as how to apply these tools to improve performance in React applications. What is a Pure Function? First off, it's important to understand the concept of a Pure Function, which will always return the same result with the same input parameters. To put it simply, the same input will always yield the same output. For example: // this is pure function function sum ( a : number , b : number ): number { return a + b ; } sum ( 1 , 2 ); // always return 3 const offset = 3 ; // this is not pure function function sumWithOffset ( a : number , b : number ): number { return a + b + offset ; } sum ( 1 , 2 ); // result depend on offset value What is a Pure Component? In React, a PureComponent is considered a component that only renders when there's a change in props or state, where the change in props or state is det
Read more