The problem with full hydration
Traditional SSR sends HTML, then ships the entire page as JavaScript to hydrate it. Even static text becomes part of a giant bundle the browser must download and execute before anything is interactive.
The island model
Islands architecture treats the page as a sea of static HTML with small islands of interactivity. Each interactive widget hydrates independently and on its own schedule.
- The shell renders as plain HTML and is immediately visible.
- A search box, a cart counter, or a carousel each become a separate island.
- Islands can hydrate on load, on idle, or on visible, so off screen widgets cost nothing up front.
Why it helps
- Less JavaScript ships because static regions never hydrate.
- Hydration is parallel and partial, so the main thread is freed sooner.
- A failing island does not block the rest of the page.
Frameworks like Astro and Fresh popularized this pattern.
Key idea
Islands architecture hydrates only interactive components, leaving static HTML untouched to slash JavaScript and speed up interactivity.