AMA — Micro-Frontend Platform

Case study · Alberta Motor Association · 2022–Present

AMA's staff software is a large React app built by multiple teams. A container shell composes independently deployed micro-frontends, while shared tooling keeps them consistent. The platform existed before I joined; my work was to extend it, harden it, and build one frontend from scratch.

This case study focuses on platform work: micro-frontend composition, shared tooling, CI, and delivery infrastructure.

new-MFE setup ~80% faster · CI ~65% faster · 27 remote modules

The problem

As more teams worked in the same app, shipping got harder. Everything shared one release, teams blocked each other, and standing up a new frontend meant copying a lot of boilerplate. The platform needed to let teams build, test, and deploy independently, on a consistent foundation.

What I built

Composition: extended the container, dev shell, and Module Federation wiring across 5+ MFE surfaces.
Greenfield MFE: built communication preferences from first commit through deployment and backend work.
Shared tooling: hardened starter templates and shared libraries with tests, error handling, deploy safeguards, compatibility, and security updates.
Delivery: moved hosting into CDK and set up one-command deploys, PR previews, and staged releases.

Architecture

A shared template and library keep new frontends consistent. Each MFE builds and deploys on its own, and the container shell composes them into one experience for staff.

Why it's built this way. For platform work, the users are other engineers. The useful work is often the boring work: templates, shared libraries, one-command deploys, and preview environments that let teams ship without asking another team to wire things up for them.

Impact

Standing up a new MFE went from about a week of boilerplate to roughly a day (~80% faster), once teams built on the shared template I hardened.
Parallelizing the test suite cut CI from about 35 minutes to about 12 (~65% faster), with no loss in coverage.
Host-side work across 5+ distinct MFE surfaces.
One MFE built from its first commit through frontend, infrastructure, deployment, and backend.
The broader POS platform supports ~80K completed transactions/month across 600+ active agents.
The platform composes 27 remote modules (22 in the lightweight integration shell), so teams can build and deploy their parts independently while staff still use one unified POS application.
Frontend delivery moved into infrastructure-as-code (CDK), with single-command deploys and automated PR-preview environments replacing manual setup.

One major frontend on this platform is the membership servicing rebuild.

Read that case study → Back to Projects →

[M]Minesweeper

[P]Paint