Understanding micro front ends
frontendmastery.com
Understanding micro front ends
1–4 of 4 posts
Re: Understanding micro front ends
#2Decent article. Was going to post a comment about how terribly wrong it could go to have each team pick their own tech stack, force the client to download all of them, and run them in a shared environment. Makes me shudder thinking about it. But they call this out towards the end.
It’s a solution to an organizational problem, but to do it well it requires serious organization and disciple. If your organization lacks the strong engineering leadership and/or doesn’t prioritize client performance then micro frontends will just make things worse for your clients.
Re: Understanding micro front ends
#3Decent article. Was going to post a comment about how terribly wrong it could go to have each team pick their own tech stack, force the client to download all of them, and run them in a shared environment. Makes me shudder thinking about it. But they call this out towards the end. It’s a solution to an organizational problem, but to do it well it requires serious organization and disciple. If your organization lacks…
It may be great solution in specific context, for example when outsourcing parts of app to different teams and you create intranet app where perf. is not that important.
Everything needs context.
Re: Understanding micro front ends
#4> "Web frameworks like Fresh, Astro and Marko promote the “component islands pattern”."
3 frameworks I've never heard of. fml. i really need to find an escape from web.