Strategies for Federated Development in Transitional Apps

[oravecz]

The benefit of a federated architecture is that very large applications may be broken up into individual features that a single team can develop, test and deploy autonomously. To date, nearly all examples of federated architectures involve single-page applications (SPA), with a library like SingleSpa to provide the top-level, client-side routing and lifecycle orchestration.

A transition back to multi-page applications, and perhaps server-side rendering, might complicate the ability for teams to build out runtime sharable and updatable applications. Are any strategies on how to use SvelteKit to enable federated development without reverting to a monolithic test/deploy stage beginning to emerge?