Layers and composition

Three responsibility boundaries

• L0 integration: Shell composes MF capabilities; the reference site and businesses own pages/SSR; Portal handles server-side API/Zone/Cookie ingress, and Administration maintains configuration.
• L1 platform: identity, permissions, directory, Gateway and shared capabilities, without owning every application’s business model.
• L2 business: independent rules, data, migrations and release cycles, consuming the platform over SDK/HTTP.

Two forms of reuse

A package shares code and types at build time. An application is an independent runtime unit integrated through the directory and Gateway. The first C-end approach uses Zone pages under one site.

Capability MF loads SDKs through application mappings; same-page business microfrontends remain deferred. Management iframes use delegated identities, while a Zone starts a separate document/runtime with client identity. A same-origin Zone is not an untrusted-script sandbox.

Data and identity ownership

Independent applications do not import Core entities or share platform business tables. They verify platform identity over APIs and still authorize their own resources and operations. Hidden menus do not replace backend authorization.

• Existing application reference →
• Server identity SDK →