Front-end architecture for scalable web applications

How a front-end is split, where state lives and how it talks to the systems behind it: the decisions that determine whether an application is still easy to change in three years.

Architecture is the set of decisions that are expensive to change later. On the front-end those are: how the application is split, where each kind of state lives, what the contract with the API looks like, and how failure is handled.

I prefer architectures that are deliberately boring. Cache aggressively, push only what changes, keep server data out of UI state, and make every view own the data it needs. Adding a feature should mean adding a query and a component, not touching something shared.

Because I have built the back-end side as well, I can design the seam between the two: a GraphQL gateway in front of legacy systems, a Node.js middleware that normalises product data, or row-level security in the database so permission checks stay out of the component tree.

What this covers

  • Splitting applications and defining boundaries
  • Separating UI state, application state and server data
  • API design with GraphQL and REST
  • Caching, invalidation and edge delivery
  • Resilience: retries, fallbacks and visible error states
  • CI/CD and automated testing

Where I did this

  • Digital Signage Studio (2025): Two apps with one API: an admin environment and a player, with UI state, application state and API data kept strictly apart, and every integration written to survive a bad network.
  • MB Sports · Klaas Nienhuis Studio · Mirari (2025): State machines for the configuration flow, with a Node.js middleware that normalises product data, handles pricing rules and brokers requests to the manufacturer's back office.
  • GeodataPro (2025): A schema-first GraphQL layer between Drupal and React, where each dashboard view fetches its own slice of data and responses are cached at the CDN edge.
  • Realtime Dashboard (2025): Next.js for the application shell, GraphQL for historical data and Supabase row-level security for access control at the database level.
  • Nautical Dashboard (2025): A GraphQL gateway that aggregates multiple legacy and third-party systems into a single consistent API.

By Guus van de Wal, Senior Front-end Developer & UI Engineer.