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:

how to use the ternary operator in javascript

How to use the ternary operator in JavaScript

Add to your JavaScript knowledge of shortcuts by mastering the ternary operator, so you can write cleaner code that your fellow developers will love.

Chizaram Ken
Feb 21, 2025 â‹… 7 min read
Using tsup To Bundle Your TypeScript Package

Using tsup to bundle your TypeScript package

Learn how to efficiently bundle your TypeScript package with tsup. This guide covers setup, custom output extensions, and best practices for optimized, production-ready builds.

Muhammad Ali
Feb 20, 2025 â‹… 7 min read
how to use react higher order components

How to use React higher-order components

Learn the fundamentals of React’s high-order components and play with some code samples to help you understand how it works.

Hussain Arif
Feb 20, 2025 â‹… 10 min read
dependency inversion principle

Understanding the dependency inversion principle (DIP)

Learn about the dependency inversion principle (DIP), its importance, and how to implement it across multiple programming languages.

Samuel Olusola
Feb 20, 2025 â‹… 8 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