Micro Frontends - A microservice approach to the modern web

By Ivan Jovanovic

Elevator Pitch

The web is changing every day and it’s so hard to follow and implement all the new and fancy stuff that is being built. Usually is not that easy to deprecate some old technology and migrate to the new one. This is the story of Micro Frontends, a microservice approach to the modern web!

Description

The web is changing every day and it’s so hard to follow and implement all the new and fancy stuff that is being built. Cool new frameworks, libraries, methodologies and new approaches to solving problems. Usually is not that easy to deprecate some old technology and migrate to the new one. There are not many developers that still want to work with Angular 1 or Backbone and moving to something new is becoming necessary. If this sounds familiar to you, then this talk is for you! There is an innovative way to migrate from the old technology, to change the applications step by step and to implement all new things that the cool kids are using. This is the story of Micro Frontends, a microservice approach to the modern web, the story that will change the way you look and develop your apps!

Ever wanted to use microservices architecture on the frontend? Want to build an app using React, Angular, and Vue together? This talk is about a thing that’s in our minds for a long time, but now’s the perfect time for it. It is called Micro Frontends, a microservice architecture on the frontend. I will show you how to write apps piece by piece and how to connect those pieces to work together. It’s so easy to split work between teams and developers and maintain those apps.

The talk will cover: 1. What are a Micro Frontends and what problem are they solving? 2. What are our choices now? 3. Examples of the implementations 4. Sync and async services 5. How can we use iframes for splitting frontend apps?

This talk will try to change the way developers look at frontend applications. They’re becoming so big, nowadays we have 90% of the client code and 10% of the backend code and that’s becoming so hard to maintain. I’ve been using this pattern for a year and so far it helped me a lot. This architecture helped my company to split the work across teams and remove the code conflicts.