Should I need to add cache option in "fetch" inside of server action if wanna cache data?

[kientrant1]

Summary

As following these points, they're mentioned in document of NextJS 14

1. Next.js automatically caches the returned values of fetch in the Data Cache on the server.
2. fetch requests are not cached when:

• Used inside a Server Action.

• Used inside a Route Handler that uses the POST method

If so, when I use "fetch" request inside of server action. Then, data will be cached or not. And do I need to add "cache" option in this situation. Can you help to clarify my concerns? Thanks!

Additional information

I'm using Next.js version 14

Example

No response

[icyJoseph]

Yeah, I guess so, the thing is that a server action is typically, used to do server side mutations, and it is a sensible default, to not cache any fetch requests made within that intention, so that you can mutate the data properly.

I'd say, better be explicit anyway. In Next 15, they reworked the defaults during SSR, and I've seen some people tripped by the implicit mechanics, the solution has been, to make fetch caching explicit, where possible.

[kientrant1]

Thanks. It make senses. Basically, I think if Client Component wanna fetch data. Then, it's better to use "Next.js API" instead of.