Creating a runtime

We've already seen that a runtime forms the centerpiece of a siteless UI implementation. While the runtime forms as an orchestrator when released and running in production, it also provides an emulator to allow local development of new modules.

This way, things such as automatic provisioning, caching rules, and runtime optimizations are all available in production – but they don't reduce developer efficiency during development.

In order to focus on the decisions that matter for our runtime, we should pick an established framework to provide the technical basis. One possible choice is Piral.

Important note

Coming up with a full siteless UI implementation is difficult. It not only requires a model for the app shell that emphasizes local development, but it also requires that the feed service and micro frontend packaging are defined and implemented while adding a custom API with reliability for micro frontends. A quick way around this is...