Microservices, but what about the UI
summary
Argument that frontends can be split into modular, deployable pieces so backend microservices stay independently deployable, demonstrated with a small system: customer service + order service + Zuul reverse proxy serving server-rendered Thymeleaf pages, enriched in-place by three lines of jQuery to pull HTML fragments. Demo shows adding a delivery date in the order service updates the UI without redeploying the customer app. Notes tooling: Spring Boot, Spring Data Rest, webjars; warns about styling consistency, JS-version clashes, history and CORS trade-offs.
AI-written summary · about
chapters (6)
related talks
36mMicro Frontends - Breaking Monoliths
46mMicro Frontend: the microservice puzzle extended to frontend
01h 03mEvolving compositional user interfaces
35mFront-end Microservices Architecture
37mDemystifying Micro-Frontends
57mMicro Frontends – a strive for fully verticalized systems
18mMicroservices Out In the Wild
44mMicro Frontend: the microservice puzzle extended to frontend
