Skip to main content

Designing a UI for Microservices

How do we design a UI when the back-end system consists of dozens (or more) microservices? We have separation and autonomy on the back end, but on the front end this all needs to come back together. How do we stop it from turning into a mess of spaghetti code? How do we prevent simple actions from causing an inefficient torrent of web requests? Join Mauro in building a .NET Core composite UI for microservices from scratch. Walk away with a clear understanding of UI composition and how to architect a microservices-ready front end.

Need help getting started?