Remote Module Loading
Importing code from another application's build at runtime, with the versioning, availability and failure questions that a normal import does not have.
A conventional import is resolved at build time and the result is in your bundle. A remote import is resolved at run time against another team's deployment: their current build, on their schedule, over the network.
That converts a compile-time guarantee into a runtime dependency, and three questions follow that a normal import never raises. Availability — what renders if the remote is unreachable or slow? A page that blanks because another team's CDN had an issue is a poor trade for deployment independence. Version compatibility — shared libraries must be negotiated, and a mismatch surfaces as a runtime error in production rather than as a build failure. Contract stability — the remote's exported interface is now an API, with all the deprecation obligations that implies.
Practical requirements: a timeout and a fallback for every remote, so a failure degrades one region rather than the page; explicit shared-dependency declarations with agreed version ranges; and integration testing against the deployed remote rather than against a local copy, since the local copy is exactly what runtime composition means you are not using.