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:

i tried kiro and here is what i learned

I tried out Kiro: Here’s what I learned

Check out Kiro, AWS’s AI-powered IDE, see what makes it different from other AI coding tools, and explore whether it lives up to the hype.

Elijah Asaolu
Aug 28, 2025 â‹… 5 min read
Go Design Pattern Article Image With Logo

Why Go design patterns still matter

Here’s how three design patterns solved our Go microservices scaling problems without sacrificing simplicity.

Peter Aideloje
Aug 28, 2025 â‹… 2 min read
how to protect your ai agent from prompt injection attacks

How to protect your AI agent from prompt injection attacks

Explore six principled design patterns (with real-world examples) to help you protect your LLM agents from prompt injection attacks.

Rosario De Chiara
Aug 27, 2025 â‹… 5 min read
Don’t Let AI Erase The Next Generation Of Dev Leaders

Don’t let AI erase the next generation of dev leaders

As AI tools take over more routine coding work, some companies are cutting early-career dev roles — a short-sighted move that could quietly erode the next generation of tech leaders if we aren’t careful.

Jack Herrington
Aug 26, 2025 â‹… 6 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