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.
Related terms
Headless Architecture
A software design pattern that separates backend logic and data from the presentation layer, letting any frontend — UI, API, agent, or CLI — consume the same business capabilities.
Salesforce Multi-Framework
A framework-agnostic Salesforce runtime that lets a standard React app run natively on the platform, with Salesforce authentication, security and governance applied automatically.
UI Bundle
The Salesforce metadata type that packages a Multi-Framework app for deployment, declaring in .uibundle-meta.xml which surface it targets.
Micro-Frontends in practice
Articles from the Funnelists Team that put this term to work.
Salesforce Platform SDK Guide for Platform Architects Building React Apps
Platform architects facing React integration challenges on Salesforce can use the Platform SDK and Multi-Framework for native security and GraphQL access without custom OAuth layers.
How Do SF Platform Architects Implement Salesforce Micro Frontends Without Framework Lock-In?
SF Platform Architects implement Salesforce micro frontends with Multi-Framework and MFE Developer Preview using sandboxed iframes and the Platform SDK to avoid framework lock-in.
How Do SF Platform Architects Build Headless Salesforce Experiences with Multiple Frameworks?
SF Platform Architects build headless Salesforce experiences by exposing core data through APIs and composing frontends from React, LWC, Vue and more—without framework lock-in.
Decouple Salesforce Frontend: Replace Experience Cloud with Your Own React Stack
Solution architects and Salesforce admins can now run full React apps natively on the platform. Learn how Multi-Framework removes Experience Cloud constraints while keeping data, security, and governance inside Salesforce.