2024-10-29
3520
#node#react
Oyinkansola Awosan
197222
114
Oct 29, 2024 â‹… 12 min read

Advanced Next.js caching strategies

Oyinkansola Awosan I'm a fun techie and passionate technical writer interested in data science, machine learning, cloud engineering, and blockchain technologies.

Recent posts:

next js link component

How to use the Next.js Link component to optimize navigation

With features like automatic prefetching and seamless integration with dynamic routing, Link helps you create a fast and responsive web application.

Chimezie Innocent
Mar 31, 2025 â‹… 5 min read
tanstack table react table

A complete guide to TanStack Table (formerly React Table)

Discover how to use TanStack Table, formerly known as React Table, to build a table UI for a variety of use cases.

Paramanantham Harrison
Mar 28, 2025 â‹… 14 min read
javascript object prototypes

JavaScript prototypes: How objects inherit properties and methods

Explore what prototypes are, how the prototype chain works, and how to use the prototype chain to create inheritance between objects.

Ibadehin Mojeed
Mar 28, 2025 â‹… 7 min read
set up Node.js with TypeScript and Express

How to set up TypeScript with Node.js and Express

Set up TypeScript with Node.js and Express, focusing on configuring key elements for a smooth development experience.

Aman Mittal
Mar 28, 2025 â‹… 9 min read
View all posts

2 Replies to "Advanced Next.js caching strategies"

  1. Thank you very much for the tools you are presenting.
    Unhappily, your article is just speaking about the Next “old” way (page router) and, which is sad too, is not taking in account the breaking changes in Next 15 new way of caching, which makes it obsolete for the biggest part :(.
    I’m feeling that this is really sad for you, as you took a lot of time, effort and dedication to make your article nice and easy to understand, full of illustrating examples, but it really suffered from bad timing (not your fault, but Next.js is obviously changing its paradigm since v13 and the app router way of doing things : of course, the page router still exists, but it does not support all the new and very useful bits of functionality).
    Anyway, maybe a little bit of editing could make this article profitable for everybody, independently of the router structure they are choosing, and the inversion of default behavior that v15 introduced ?

    1. Thank you so much for the kind words and for sharing your thoughts! We’re glad that the examples and explanations were clear and helpful, even if the focus was on the page router approach. It’s always a challenge keeping pace with these exciting changes, but feedback like yours helps keep the discussion going.

Leave a Reply