Server components changed how I structure data

The obvious win from server components is fewer client-side waterfalls. The less obvious one, and the one that actually changed how I structure a codebase, is that “where does this data live” and “where does this need to be interactive” stopped being the same question.

That split forces a cleaner boundary between layout components and the islands of real interactivity inside them — closer to how I’d already been thinking about performance budgets, but now the framework enforces it instead of asking nicely.

Full breakdown of the pattern, with a real project’s before/after, coming soon.