The Future of Micro-Frontends: How to Combine Module Federation with Server-Side Rendering (SSR)
Client-side Module Federation has a well-known weakness, the browser downloads a shell, then fetches...
Tag archive
Client-side Module Federation has a well-known weakness, the browser downloads a shell, then fetches...

Large JavaScript bundles severely hinder web application performance, leading to slow load times and high bounce rates. This article provides a practi

The file that decides what every device runs was plain text. Now it carries a signature and a release counter, so a device refuses a map older than one it has already accepted, and a remote whose version fails to load on two launches skips the CDN on the third and runs from its copy, with nobody paged. The last post of the series.

The CDN goes down and the app still starts, from a copy of each remote built into the binary. In a CDN launch, a remote that fails to load drops to its own copy while the other stays on the CDN, and Try again finally retries.

Every launch, the app asks the CDN which remote versions it may run. Then an operator ships a new one to an installed app with one directory and one line of JSON, and rolls it back the same way. Plus what Apple and Google permit, quoted from the current texts.

The remotes leave the dev server: built for production, signed at build time and served from a CDN that is a directory and a port. The registry sits in the middle, and one table says which changes still cost an app-store release.

A remote ships JavaScript only, so the host lends it a native screen through one promise: a routing table, a TurboModule, and a Quick Battle in SwiftUI and Compose built so every exit settles the promise.

A shared testing package gives every remote the same WCAG bar: contrast, touch targets and status semantics checked in the packages that own them, each team's own screens checked in its own suite, and a failing test that found a button nobody could measure.

Three federated apps carry three copies of the same greys until a design-system package moves to the seam: gluestack-ui components and NativeWind under Re.Pack, one shared singleton, and one theme toggle that re-themes every remote at once.
Durante el pico de tráfico del último Black Friday, la plataforma de comercio electrónico de un...

The same PokéAPI data arrives over REST and GraphQL through one RTK Query slice, one tag invalidates across both, and the honest question is when Apollo's normalised cache is worth two caches during the transition.

TanStack Query and Zustand rebuild the app Redux Toolkit and RTK Query just built; both work, and what separates them is what happens when independent teams stop coordinating.