Building Micro-Frontends • Luca Mezzalira & Lucas Dohmen • GOTO 2022

[@andresdigi25]

in our company we use s to modernize our UI gradually. The old version with thousands of lines of code running in a monolithic application using old frameworks and new apps are microservices using apis and react front ends. We glue everything with s and we used cognito for the security. And the final users see a web page with different sections

[@kaizentv711]

Overwhelmed 0

[@Zealotux]

Interesting, how is SEO handled?

[@CliffordFajardo]

@@Zealotux - if this is an internal app, meaning you need to be authenticated to view the content, there is no SEO to think about because web crawlers/bots can only view unauthenticated content (guest content) Microfrontends for unauthenticated / guest experiences are a bit more complex due to having to worry about SEO / performance (speed lighthouse score impacts SEO rankings) etc. Curious to hear more thoughts on guest/authenticated experiences though

[@asdqwe4427]

I still think that we should avoid the complexity of possible

[@My50c]

totally! micro-frontends shouldn't replace the current frontend architectures, they should add new possibilities to the frontend ecosystem

[@ProBloggerWorld]

Micro Frontends are a solution as well as a smell, which is revealed in the classical question about style guides and their (not) sharing around 25:00. Especially 25:57 is frustrating: there is no "CSS CDN sharing solves everything". CSS requires a certain HTML structure. And if you share CSS - why not bake it consequently bake it into your Component library and use this instead of relying on complex integration scenarios using iFrames? Developers tend to use and favor complex solutions over technical possibilities. Also the host's mention of Google Maps has nothing to do with the quality of iFrames. It is a burden. What counts in this example is the user experience which is great despite (!) using iFrames. My sound advice in regards to MFs is simple: use it as ultima ratio.

[@hakanozsoy8878]

D