I've been prototyping this approach recently -- I think you can go simpler / leaner yet. The iframe angle is probably the most universal, and easiest way to in

I've been prototyping this approach recently -- I think you can go simpler / leaner yet. The iframe angle is probably the most universal, and easiest way to include legacy apps / sites. It does present challenges with authentication, as cookies cannot be persisted by a framed context. Local storage still works, but that requires some changes in the legacy apps. As far as the "orchestrator" goes, I don't see the point of using a nearly-legacy framework (yes, a jab at Angular) when this can be done in plain vanilla JS with postMessage. Some balk at using events, but in this context messaging between clients could be a light, elegant solution to the communication / synchronization problem. Finally -- this is bound to fail in actual real-world applications, because legacy apps are very likely to include everything and the kitchen sink, and simply wrapping them in frames doesn't solve the problem of a bloated do-everything spaghetti monster. As an architectural approach for developing new, modular front-end solutions, this is promising. Multiple small teams responsible for small, single-purpose apps, stack-agnostic in aggregate -- this way of handling scale could reduce the overall complexity, making development and maintenance a little easier.