#astro#next.js#frameworks

Astro 5 — should you migrate from Next.js

Astro positioned itself as content-first. By v5 it has Server Islands and full DB integration. When it beats Next.js.

Astro renders to static HTML by default. Zero JavaScript shipped unless you opt in via "islands" of interactivity.

Server Islands (v5): per-component server-side fetching with caching. Closes the gap with Next.js for dynamic content.

When Astro wins: blogs, docs, marketing sites, e-commerce browse pages. Bundle 5-10x smaller than Next.js.

When Next.js wins: full app shells, complex client interactivity, when team already knows React deeply.

Other articles
(01) Astro 5 in 2026 — what to use for a marketing site Astro 5 has settled in as the default for landings and blogs. What is actually useful from the new features — Server Islands, Content Layer, View Transitions. → (02) Server Components two years in RSC was the future of React in 2024. By 2026 it is split between believers and pragmatists. Where it actually helped. → (03) Next.js 15 Server Actions in production Server Actions reduce CRUD code by 30-50%. They also have edge cases. What we found shipping them at scale. → (04) Next.js vs Nuxt 3 — pick by your team Next.js for React teams, Nuxt for Vue. Technically equivalent. Pick by what your team already knows. → (05) 1C-Bitrix in 2026 — still worth picking, or are alternatives better 1C-Bitrix is still the leader in the Russian market, but over 11 years better options have appeared for specific jobs. Where Bitrix is fine, and where it is an overpay. →