Right now I am working on a talk around this area and an idea came to my mind that I think is worth a discussion here on HN. In today's front-end technologies

Right now I am working on a talk around this area and an idea came to my mind that I think is worth a discussion here on HN. In today's front-end technologies with webpack and webcomponents why wouldn't you compose application that call different services and compose the UI based on these services. For example, you have a login/welcome component that will call the auth service and will check if the user is logged in or not and show the appropriate message or login screen. If the Auth service is down you can simply show a message. This way, each component is aware of the service it has to use and you can package it into the application deployment process. It's worth a thought that if you already have micro-services you should also break your application apart and not have a monolithic front-end. I am not an Android/iOS guy so I'm not sure if this is even viable there but these days, I'm pretty sure we'll start seeing front-ends that are composed around small single-responsibility services. One of the biggest advantages of that is that components and services are independent, you can split the work between teams and the application deployment will join everything together.