---
title: "Comment by Tarun Sharma on \"App Router vs Pages Router: What Actually Changed in Next.js\" | Hashnode"
description: "Good breakdown of the mental model. Two things worth adding for anyone migrating now. The fetch caching default flipped in Next 15, fetch is no longer cached by"
url: "https://hashnode.com/posts/app-router-vs-pages-router-what-actually-changed-in-next-js/6a92edb4ec28ed1c41e0e193/comment/6a94320289b81ef5057a192d"
---

[Discussion](https://hashnode.com/posts/app-router-vs-pages-router-what-actually-changed-in-next-js/6a92edb4ec28ed1c41e0e193)

Comment [App Router vs Pages Router: What Actually Changed in Next.js](https://hashnode.com/posts/app-router-vs-pages-router-what-actually-changed-in-next-js/6a92edb4ec28ed1c41e0e193)

[Aug 30](https://hashnode.com/posts/app-router-vs-pages-router-what-actually-changed-in-next-js/6a92edb4ec28ed1c41e0e193/comment/6a94320289b81ef5057a192d)

Good breakdown of the mental model. Two things worth adding for anyone migrating now. The fetch caching default flipped in Next 15, fetch is no longer cached by default so you have to opt into force-cache explicitly, which trips up people following older tutorials that assume it caches. And use client marks a boundary, not a whole subtree. You can still render server components inside a client component by passing them as children or props, so you rarely need to push the directive as far down the tree as people assume.
