When you introduce a microservice architecture you expect small, decoupled and scalable services. Unfortunately, for frontend development this is hard to achieve, and you will often end up maintaining a "frontend monolith". At his #AOEconf17 talk, Florian Brandel gives insights at challenges and solutions when creating UIs in a microservice architecture.
https://www.aoe.com
2. MICRO FRONTENDS
WHAT WE HAVE LEARNED FROM MICROSERVICES…
‣ Small is better
‣ Single Responsibility
‣ Easier Scalability
‣ Independent Deployment
‣ Mix multiple technologies
4. MICRO FRONTENDS
MICRO FRONTENDS
In this approach, a web application is broken up by its pages and features, with
each feature being owned end-to-end by a single team. It allows each feature to
be developed, tested and deployed independently.
18. MICRO FRONTENDS
OUR LEARNINGS
‣ No one-fits-all solution
‣ Micro Frontends help Teams to work independently
‣ But: Who is overall responsible for the Frontend?
‣ Many challenges to deal with…
‣ Mix of technologies
‣ Error Handling / Resilience
‣ Local Development Environment