Echo JS 0.11.0

For a front end... *ONLY* do this if you *REALLY* need it... Some really large corporations need this kind of thing (think hundreds of developers writing interconnected applications).  If you're on a relatively small team and unlikely to have over 20 developers, this will create more friction than it solves imho.

While this targets indeed large applications the numbers (> 100 developers) are not quite accurate. We deployed this solutions for some customers in the range of 10-25 developers and both, the client and their developers, love it and are by far more productive. So we are convinced of its advantages.

It does not only simplify development (especially onboarding time, but also time to market), but it makes it super easy to have a progressive rollout. No code change required. Personalized experience? Also out of the box.

Still, it is certainly not for everybody and the target application area are large tools (e.g., highly interactive portals, administration or configuration apps, ...).

I do agree... and the number 100 devs is probably a bit over the top.  It's only that a lot of people will try approaches like this on a very small scale and will run into serious problems of orchestration at a small scale that tends to outweigh the advantages.  I've worked on similar approaches in the past and see both sides.

My advice is simply caution and YAGNI to an extent.  Much like most Enterprisey patterns in general, many lead to more friction than they're worth.