An Unexpected Solution To Microservices UI Composition
written by Arif Wider
So you have decided to opt for Microservices in order to achieve maximum autonomy for your teams. Still, at the front end your services still have to be joined into one single page. This requirement leaves you with two options: Either have one single UI layer which all teams depend on or let each service render its own UI and compose these UI pieces later on. In the course of transforming the AutoScout24 platform — one of Europe’s leading internet car portals — to an AWS-hosted Microservice architecture, we favored autonomy and therefore decided for the Microservices UI composition approach. During this process we faced all the typical challenges with regard to UI Composition, such as performance, consistency, isolation, and testing. Learn how we started off with a rather complex attempt and then managed to greatly improve and simplify our solution.
Slides
Video
