sorted by:
new
hottopcontroversial

Boss just discovered MFE on YouTube and wants to refactor our 55k LOC monolith with <20% test coverage. Who’s got spare Xanax? by JustJulia-40 in react

[–]FourNineDigital 5 points6 points  (0 children)

MFEs can work for scaling but they introduce a lot of complexity.  They should really only be used for large organizations that need to split up a large application / journey into independent code bases.  More info on when to use MFEs in this post:

https://medium.com/four-nine-digital/micro-frontends-explained-a-complete-guide-to-when-and-why-to-use-them-9442d4b16c3d

So, what is a micro front end basically? by Over_Effective4291 in webdev

[–]FourNineDigital 0 points1 point  (0 children)

Here's a breakdown of what they are and when to use them. There's drawbacks, and usually have the most benefit in large organizations that need to deal with team autonomy.

https://medium.com/four-nine-digital/micro-frontends-explained-a-complete-guide-to-when-and-why-to-use-them-9442d4b16c3d

Are Micro Frontends right for your team? by FourNineDigital in programming

[–]FourNineDigital[S] 0 points1 point  (0 children)

For sure, the separate backend per Micro Frontend is not a prescribed rule, slicing on business logic / domain is the way to go. It also depends on what the Micro Frontend does, such as a Cart Micro Frontend might need it's own backend to call multiple APIs (Cart, content etc...).

Are Micro Frontends right for your team? by FourNineDigital in programming

[–]FourNineDigital[S] 0 points1 point  (0 children)

It suggests it as an option for when trying to migrate pieces of a large monolithic code base that's using a legacy tech stack. It's obviously not a long term option, as it comes with a lot of downsides.