M

Micro-Frontends

An architecture that composes several independently built and deployed frontend bundles instead of one monolithic app — each owning a domain and shipping on its own cadence.

What it is

A micro-frontend architecture composes an interface from several independently built and deployed bundles rather than one monolithic application. Each bundle owns a domain, ships on its own release cadence, and is developed by the team responsible for it.

Why it matters

It is what stops a large frontend becoming a single release train where every change waits on every other. On Salesforce it also means a team can ship its own surface without redeploying the whole interface, while every bundle still shares one org’s data and permission model.

Key components

  • Independently deployable bundles
  • Domain ownership per bundle
  • Independent release cadence
  • Shared data and permission model

How it connects

On Salesforce each piece is a UI Bundle targeting the surface it belongs on — an internal app, an Experience site — so the composition is a deployment decision rather than a framework feature.

Good to know

Salesforce does not ship a "micro-frontend" product. It is an architectural pattern you compose from UI Bundles, and it is worth ruling out for a small app: the coordination cost is real and only pays off at scale.

Need Help Implementing This?

We specialize in putting AI and Agentforce to work for Salesforce customers. Let's talk about your use case.

Book Intro Call