Scalable Web Production

Twentieth and final article in a series about migrating from legacy architectures to a modern Nuxt 4 stack. From Parts to Whole The previous fifteen articles describe individual pieces — the GraphQL gateway, code generators, performance, infrastructure, security. This article brings them together and answers the question that matters to decision-makers: what does the complete…

Nineteenth in a series about migrating from legacy architectures to a modern Nuxt 4 stack. Architecture Decisions Have Consequences — Measure Them Architecture decisions accumulate, and their combined effect only becomes visible under real load. Before production, a large enterprise application was load-tested with production-equivalent patterns, not synthetic traffic. k6 replayed a model derived from…

Migrating from a legacy application to a modern Nuxt 4 stack is not just about new frameworks and better performance numbers. The real shift is moving from reactive firefighting to proactive observability — knowing what is slow, why it is slow, and how the platform behaves under real load. This observability stack has three pillars:…

Seventeenth in a series about migrating from legacy architectures to a modern Nuxt 4 stack. The Inconvenient Truth About Node.js Servers Node.js is optimized for event-driven I/O, not for long-lived servers that render thousands of pages per hour. Over time, the V8 heap grows and objects such as GraphQL responses, Vue server renderer allocations, cached…

Sixteenth in a series about migrating from legacy architectures to a modern Nuxt 4 stack. The Environment Problem Any non-trivial application needs multiple environments: development, test, production. In a large enterprise application, feature branches ideally each get an isolated environment so developers can share a live preview without blocking one another. Configuration is where the…

Fifteenth in a series about migrating from legacy architectures to a modern Nuxt 4 stack. Security in SSR Is Different An SSR application has a very different attack surface from a client-side SPA. The server is responsible for rendering HTML with embedded state, generating tokens, setting cookies, and proxying API calls — all before the…

Fourteenth in a series about migrating from legacy architectures to a modern Nuxt 4 stack. The Hydration Dilemma SSR gives you a fast first paint: complete HTML that the browser can render immediately. Then the framework’s JavaScript arrives, gets parsed, compiled, and executed to hydrate the page—wiring up event listeners and making everything interactive. During…

Masterclass in building a modern Nuxt 4 stack that hits Lighthouse 97–100 on mobile without going “zero‑JS”. Performance Is an Architecture Decision In large enterprise applications, performance rot rarely starts with “slow code.” It starts when the architecture cannot absorb new features without stacking more JavaScript, more requests, and more complexity on the critical path.…