Hi all! I'm new to the forum, I really like NextJS and I've even used it in my production projects. But I used the Pages Router approach. And now I decided that it’s worth keeping up with the times and trying App Router.

I have two related questions:
I have a project where the backend developer created an endpoint for dynamic pages, where he sends header, footer, content and... meta tags for the head tag.
Reading the doc about the wonderful, declared function https://nextjs.org/docs/app/api-reference/functions/generate-metadata#generatemetadata-function

However, with the new App Router approach, when we no longer use getServerSideProps and do not push data deep into the entire page including components, I have a probably stupid question:

- Is it normal that I will fetch extra data into the generateMetadata function (I only need meta tags, and there’s everything there, including header, footer and content)? Or should I ask the backend developer to split this endpoint into parts? Or I can pass already fetched data into this function?

I may know the answer to this question, but I would like to make sure. I know that fetch function caches data automatically if it is a server component. Does this mean I shouldn't worry about it? And on the server, the fetch function will be called only once, and the second time it will use the data from the cache?

- The next question arises from the previous one. Previously, I used Redux on a page component to save all the data received from the getServerSideProps function so that it could be used deeper in internal components. Should I do this now, or, if the data is indeed cached in the server components, should I just call the fetch function all the time (in the inner components also)?