Using legacy code with micro frontends
Download as PPTX, PDF2 likes281 views
Ran Wahle discusses using micro frontends to integrate legacy code into a modern single page application (SPA) in a peaceful way. A demo is shown integrating three sample applications - one using jQuery, one using Angular 6, and one using Angular 5 and Firebase. Micro frontends allow each application to have its own URL routing and inner routing while reusing backend services. Wrapping applications as custom elements is also discussed as an alternative to iframes for less isolation while still maintaining independence. The talk concludes that micro frontends can help extend legacy code and blend applications together to achieve "world peace" between new and old approaches.
Using legacy code with micro frontends
- 1. Live peacefully with your legacy Ran Wahle
- 2. About me ● Programmer at Tikal ● Old ● Working for world peace
- 4. That peace - Between old and new
- 5. Let’s stop with militant sayings such as... Legacy code should Move away Who wrote this sh..t ? We are in 2018. Why use ...
- 6. You can’t beat legacy Rewriting is expensive You’ll have to reverse engineer old code Your management probably won’t let you
- 7. Micro frontends to the rescue If you can’t beat it, move away Have another micro app Interact with it
- 8. What do we need? SPA look & feel “Router-outlet” for micro apps Micro-service like integration
- 10. Our demo Three micro apps World cup teams (jQuery) World cup games (angular 6) World cup team details (angular 5 & Firebase) Shell app using micro frontends library
- 11. We had to use iframes… Because we are dealing with legacy
- 12. Make shell App
- 13. Register apps
- 14. Routing Each micro app gets its own url The shell app will present micro app by URL
- 15. Routing implementation Listen to popstate event Match route Invoke handler Read more
- 16. Blend legacy app in
- 17. Inner routes Whenever route change inside a micro app, the browser address bar should reflect that. When we reload, the micro app should be at Its last route
- 18. Events
- 19. Run setState on the micro-app
- 21. Change route in micro app
- 22. Service bus
- 23. Let’s reuse legacy app services
- 24. We have used iframe but... Iframes are too isolated We cannot really control their styling Heavy bundles Their performance are poor
- 25. Web components Less isolated but still independent We may create custom element Inside it, we may use whatever we want We can give up the global pub-sub and use the DOM But… it won’t help us with our efw years old legacy
- 26. Demo - Run one app as component
- 27. Let’s wrap We can use micro frontends to extend legacy code We blended some micro apps into one SPA We worked with inner route We have reused services And achieved world peace(?)
- 28. Thank you Ran Wahle @ranwahle [email protected] [email protected] Demo code: https://github.com/ranwahle/micro-frontends-demo