Advanced Single-SPA Architecture

Understanding advanced single-spa architecture helps you work with single-spa confidently. Here you will learn the core ideas behind advanced single-spa architecture, see working code, and pick up best practices used on real teams.

Advanced Single-SPA Architecture Overview

Advanced Single-SPA Architecture lets you structure single-spa work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep advanced single-spa architecture focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { registerApplication, start } from 'single-spa';

registerApplication({
  name: '@org/app',
  app: () => System.import('@org/app'),
  activeWhen: ['/app'],
});

start();

single-spa orchestrates multiple framework apps on one page through a root config.

Advanced Single-SPA Architecture Example

registerApplication({
  name: '@org/app',
  app: () => System.import('@org/app'),
  activeWhen: ['/app'],
});
start();

Start from a minimal Advanced Single-SPA Architecture example and grow it only as needed.
Keep configuration explicit so Advanced Single-SPA Architecture behaves the same in every environment.
Name things clearly so teammates understand your Advanced Single-SPA Architecture at a glance.
Add tests around Advanced Single-SPA Architecture early to lock in expected behaviour.

Single-SPA Cheatsheet

Core single-spa APIs related to advanced single-spa architecture.

API	Example	Purpose
registerApplication	`registerApplication({ name, app, activeWhen })`	Register a micro frontend
activeWhen	`activeWhen: ['/checkout']`	Route ownership
start	`start()`	Begin routing
bootstrap	`export async function bootstrap()`	One-time setup
mount	`export async function mount(props)`	Render the app
unmount	`export async function unmount(props)`	Clean up the app
import map	`systemjs-importmap`	Locate app bundles

How Advanced Single-SPA Architecture Works in Single-SPA

Advanced Single-SPA Architecture is part of how single-spa lets multiple applications — even in different frameworks — coexist on one page. A root config registers each app and controls when it is active.

single-spa orchestrates multiple framework apps on one page through a root config.

A root config registers apps and calls start().
Each app exports bootstrap, mount, and unmount lifecycles.
activeWhen decides which routes each app owns.
Import maps resolve each app's bundle at runtime.

Practical Guidance for Advanced Single-SPA Architecture

For reliable micro frontends, advanced single-spa architecture should isolate failures and keep shared state minimal. Let each team own its app end to end while agreeing on a few shared contracts.

Concern	Recommendation
Isolation	One app's crash should not break others
Shared state	Prefer shared utility modules over globals
Routing	Keep activeWhen rules explicit and non-overlapping
Deployment	Release via import-map updates per app

Common Mistakes

Skipping error handling and edge cases when wiring up advanced single-spa architecture.
Leaving advanced single-spa architecture untested, so regressions slip into production.
Over-engineering advanced single-spa architecture before you actually need the extra flexibility.
Ignoring documentation, which makes advanced single-spa architecture hard for the next developer to change.

Key Takeaways

Advanced Single-SPA Architecture is a core part of working effectively with single-spa.
Start small and keep advanced single-spa architecture focused on a single responsibility.
Apply consistent patterns so advanced single-spa architecture scales across your project.
Test and document advanced single-spa architecture to keep it maintainable over time.

Pro Tip

When you get stuck on advanced single-spa architecture, reduce it to the smallest reproducible example first — most single-spa issues become obvious once the noise is gone.