Next.js Discord

Discord Forum

Best practices regarding server and client components in the Next JS App Router

Unanswered
Tomistoma posted this in #help-forum
Open in Discord
TomistomaOP
I have been wondering for a while about the mindset I should approach structuring my web application with.

My approach was to minimize the use of client components and focus on storing state in the url or using the next js cache to store global state.
Lately I have been thinking why would I ever use a global management state tool like Redux or Zustand and is it a bad practice to use those tools instead of the solutions server components provide.

Another thing I have been struggling with is, is it a "bad practice" to for example make a whole page a client component I know that the component will act as a server component and later on will be hydrated so what benefits do I lose when using a client component as my page I have been trying to avoid that in my projects.


Next JS 13 introduces a lot of new way of thinking about structuring your application and since it s quite recent there s not many resources on how to do that so would appreciate the help. If there are any resources you could share please share them with me ( outside of the obvious stuff like the docs which I have thoroughly read)

1 Reply

TomistomaOP
Bump