Newline Commerce demo app

Performance matters

The Rendering Triforce

Rendering in Newline Commerce (demo)

Introduction to the Course

Static RSC - the new default

Getting data, statically

Update data, with Server Actions

Static Pages with Dynamic data

Static is great, you want static

Page-level "revalidatePath"

Datasource-level "revalidateTag"

Up-To-Date Static Rendering

Client-side data fetching recap

Relaying with SWR

Client-Server Relaying

Mix Static and Dynamic Rendering

Partial Prerendering (PPR)

Congratulations!

Conclusion

The **Blazing Fast Next.js with React Server Components** course equips you with the skills needed to master Next.js Static Rendering, coupled with Server Actions but also client-side and dynamic rendering. From foundational concepts to practical implementation, you'll gain a deep understanding of how to leverage Next.js for optimal performance and dynamic content delivery.

## **Blazing Fast Next.js with React Server Components**

### Build a Content Application with Dynamic Data - Newline Commerce

Welcome to the "Blazing Fast Next.js with React Server Components - Design patterns to accelerate Next.js Apps with Static Rendering and Server Actions" course. Throughout this program, we will guide you through the intricacies of Next.js, focusing on Server Actions and static rendering techniques. In this informative journey, we will collaboratively construct a content application named Newline Commerce.

Join us as we explore the foundations of Next.js, implementing dynamic data and server-side actions to bring Newline Commerce to life. This course is your gateway to mastering the art of server actions and static rendering in the context of real-world web development.

### How The Course Works

- The Blazing Fast Next.js with React Server Components course is a 6-module online program where you will delve into Next.js powerful patterns such as Server Actions, Static Rendering, Client-Server Relaying or Partial Prerendering. Learn to deliver fresh content to your end users with optimal performances and cost efficiency.
- Remote: Take the course from anywhere, allowing you to participate from the comfort of your preferred location.
- Self-paced: Tailor the course to fit your schedule. With a self-paced structure, you have the flexibility to learn at your own pace, ensuring a stress-free educational experience.
- Community: Engage with other students in a collaborative learning environment. Share insights, discuss challenges, and expand your understanding within a supportive community.
- Structured: Experience a cohesive and organized learning journey. The course is structured to guide you through each module in a logical and progressive fashion, ensuring a comprehensive understanding of Next.js Server Actions and Static Rendering.

### The Challenge

Navigating the realm of Next.js can be a daunting endeavor for many aspiring developers. As you embark on your journey to master this powerful framework, you may encounter several challenges:

- **Complexity Overload:** Next.js, with its robust capabilities, can overwhelm newcomers. Understanding the intricate balance between Next.js server-centric features and data update requirements requires a structured approach.
- **Dynamic Content Dilemma:** Implementing dynamic content in web applications often poses a challenge, especially when it comes to delivering fresh data efficiently to end users.
- **Performance Concerns:** Ensuring optimal performance while maintaining cost efficiency is difficult. Achieving this balance with Next.js demands a nuanced understanding of its patterns and practices.
- **Lack of Cohesive Learning Resources:** Piecing together information from various sources can be time-consuming and confusing. A structured learning path is essential for a comprehensive understanding of Next.js.

### The Frustration

Newcomers often find themselves frustrated by the lack of clarity and guidance in mastering Next.js. The complexity of static rendering aside from trivial use cases can be a significant roadblock, leading to confusion and hindered progress.

### How This Course Helps

The "Blazing Fast Next.js with React Server Components" course is designed to address these challenges head-on. Through a carefully crafted curriculum, you will gain a clear understanding of Next.js, overcome common hurdles, and confidently apply static rendering with revalidation in your web development projects.


### Unlock the Potential of Next.js in 2024

In the dynamic landscape of web development, staying ahead is key. Here's why learning Next.js in 2024 is advantageous for you:

1. **Enhanced Performance:**
Next.js continues to evolve, offering enhanced performance features that cater to the growing demand for faster, more efficient web applications.
2. **Industry Relevance:**
As of 2024, Next.js maintains its position as a leading framework, backed by a vibrant community and widespread adoption in the industry. Learning it now ensures you align with current development trends.
3. **Scalability for Modern Applications:**
In an era where scalability is paramount, Next.js provides the tools to build scalable applications that adapt to the demands of modern web development.
4. **SEO Optimization:**
Next.js server-side rendering capabilities contribute to improved SEO performance, a crucial factor for ensuring your web applications are discoverable and accessible.
5. **Developer-Friendly Ecosystem:**
With an ever-expanding ecosystem and a focus on developer experience, learning Next.js in 2024 means immersing yourself in a framework designed to streamline your development workflow.

Equip yourself with the skills to thrive in the current web development landscape. Learning Next.js in 2024 positions you at the forefront of technology, offering a competitive edge in your professional journey.

Design patterns to accelerate Next.js Apps with Static Rendering and Server Actions

Learn how to build blazingly fast websites with Next.js. Static rendering is often underrated: it’s very fast, very cheap, but hard to use in advanced scenarios. This course introduces students to personalization with static rendering by using React Server Components, the latest paradigm shift in React. By the end of this course, you'll have learned advanced Next.js concepts like server actions, static revalidation, client-server relaying, or partial prerendering, and you'll know when and how to apply different server rendering strategies in large, production-grade Next.js applications. This course mixes recent advanced concepts like Server Action and static rendering in a way that students won’t find in the documentation. Not only will this apply to any content application but also it will apply to dashboards or multi-tenant SaaS.

Blazing Fast Next.js with React Server Components

Fetch and cache data from a database inside a React Server Component.

Handle form submissions using Next.js Server Actions.

Perform client-side data fetching in Next.js with SWR.

Why the performance of a content application matters and how it's related to different rendering strategies

How to statically fetch data on a server with React Server Components (RSC)

How to update static pages with fresh content via data revalidation in Server Actions

How to perform relaying with SWR, a React Hooks library for data fetching

How to mix dynamic and static rendering via Partial Prerendering (PPR), an experimental feature introduced in Next.js 14

In the previous lesson, we have seen that 

 allows us to invalidate a static render and compute a new one with up-to-date data.

Relying on paths to invalidate static pages on updates means that we think in terms of “pages”. 

But our product list function is not tied to a specific page: it’s reused both on the home “/” and the “/products” pages.

This method requires us to revalidate all pages that display the product lists, which can be inconvenient if the site evolves frequently

revalidatePath("/")
revalidatePath("/products")
revalidatePath("/another-page-with-products")
...

Rather than invalidating each page, we should probably invalidate the list itself. 

Let's think about static rendering as a caching mechanism again. 

, the page path (~ it's URL) was used as a cache key. Refreshing the home page is as simple as revalidating the "

 data fetching function, it just calls the database directly, so we don’t have a natural cache key associated to it that we can invalidate.

That’s why the first step is “tagging” our database call. The “tag” will act as a cache key that lets us tell Next the response for this database call is stale and requires a new update.

Here is a schema showing how we can invalidate both pages from a single shared tag:

In order to tag a data fetching function, we need the 

. We can set the “tags” option so we can later invalidate this “tag”.

// src/fetchers/products.ts
import { unstable_cache } from 'next/cache'

const productsTag = "products" // a unique tag

// First step: we must "tag" the data fetching method
export const rscGetProducts = unstable_cache(
    getProducts, [], { tags: [productsTag] }
    )

 doesn't require any unstable feature, it works fine out-of-the box in Next.js 13 and 14.

fetch(`https://...`, { next: { tags: ['products'] } })

However it can be used only when your data are available via an HTTP call. For instance, fetch is relevant if you store your products in a third-party headless CMS. Here, since we call our own database to get the product list, we can't use it and we rely on 

The "next" option is available because Next.js 

---
title: Datasource-level "revalidateTag"
privateVideoUrl: https://stream.mux.com/vDgObiTp6XSFbt4tnrK00ifrDKcBpHyZHiK12cFDmyp00.m3u8
isPublicLesson: true
---

## Limitations of `revalidatePath`

In the previous lesson, we have seen that `revalidatePath` allows us to invalidate a static render and compute a new one with up-to-date data.

Relying on paths to invalidate static pages on updates means that we think in terms of “pages”. 

But our product list function is not tied to a specific page: it’s reused both on the home “/” and the “/products” pages.

This method requires us to revalidate all pages that display the product lists, which can be inconvenient if the site evolves frequently

```js
revalidatePath("/")
revalidatePath("/products")
revalidatePath("/another-page-with-products")
...
```

Rather than invalidating each page, we should probably invalidate the list itself. 

## First, we need a tag

Let's think about static rendering as a caching mechanism again. 

With `revalidatePath`, the page path (~ it's URL) was used as a cache key. Refreshing the home page is as simple as revalidating the "`/`" path.

But there is no URL tied to our `getProducts()` data fetching function, it just calls the database directly, so we don’t have a natural cache key associated to it that we can invalidate.

That’s why the first step is “tagging” our database call. The “tag” will act as a cache key that lets us tell Next the response for this database call is stale and requires a new update.

Here is a schema showing how we can invalidate both pages from a single shared tag:

![Revalidation with a tag](https://d2uusema5elisf.cloudfront.net/courses/blazing-fast-next.js-with-react-server-components/module_03/lesson_03.03/public/revalidatetag.png)

## Tagging with the unstable_cache

In order to tag a data fetching function, we need the [`unstable_cache`](https://nextjs.org/docs/app/api-reference/functions/unstable_cache) from `next/cache`. We can set the “tags” option so we can later invalidate this “tag”.

```js
// src/fetchers/products.ts
import { unstable_cache } from 'next/cache'

const productsTag = "products" // a unique tag

// First step: we must "tag" the data fetching method
export const rscGetProducts = unstable_cache(
    getProducts, [], { tags: [productsTag] }
    )
```

## Tagging with fetch

Tagging with `fetch` doesn't require any unstable feature, it works fine out-of-the box in Next.js 13 and 14.

```tsx
fetch(`https://...`, { next: { tags: ['products'] } })
```

However it can be used only when your data are available via an HTTP call. For instance, fetch is relevant if you store your products in a third-party headless CMS. Here, since we call our own database to get the product list, we can't use it and we rely on `unstable_cache` instead.

:::note
The "next" option is available because Next.js [patches the `fetch` function](https://nextjs.org/docs/app/api-reference/functions/fetch#optionsnexttags) to add some custom behaviour.
:::

:::warning
You can wrap a fetch call into an unstable_cache, but that's redundant. If you use HTTP calls, no need for unstable_cache.
:::

## Invalidating data

Tagging was really the hard part: now we can just revalidate the tag in Server Actions, exactly like we did with `revalidatePath`.

The code below illustrates revalidating the list when a new product is added.

```tsx
// src/fetchers/products.ts
"use server"
import { addProduct } from "@/db/products";
import { productsTag } from "@/fetchers/products";
import { revalidateTag } from "next/cache";
import { redirect } from "next/navigation";

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Blazing Fast Next.js with React Server Components

WELCOMEIntroduction

Introduction:

Start Here

Module 1: Introduction to the Course

Lesson 1: (1:51)

Newline Commerce demo app

Lesson 2: (1:31)

Performance matters

Lesson 3: (3:00)

The Rendering Triforce

Lesson 4: (1:37)

Rendering in Newline Commerce (demo)

Module 2: Static Pages with Dynamic data

Lesson 1: (6:51)

Static RSC - the new default

Lesson 2: (6:38)

Getting data, statically

Lesson 3: (6:30)

Update data, with Server Actions

Module 3: Up-To-Date Static Rendering

Lesson 1: (6:09)

Static is great, you want static

Lesson 2: (7:07)

Page-level "revalidatePath"

Lesson 3: (8:43)

Datasource-level "revalidateTag"

Module 4: Client-Server Relaying

Lesson 1: (10:18)

Client-side data fetching recap

Lesson 2: (9:16)

Relaying with SWR

Module 5: Partial Prerendering (PPR)

Lesson 1: (9:43)

Mix Static and Dynamic Rendering

Module 6: Conclusion

Lesson 1: (5:21)

Congratulations!

Datasource-level "revalidateTag"