DEV Community

loading...

Discussion on: Thoughts about Micro Frontends in 2020

Collapse
jsalinas11 profile image
Jordan

Well I disagree. We've used microfrontends where I work for about a year and a half now. It has really simplified my job. Apps are significantly smaller which means significantly less complex. There's a much lower chance of breaking anything. And it forces us to write clean reusable components. No more insane spaghetti code monoliths.

Collapse
pavelloz profile image
Paweł Kowalski

Thats why i wrote in 5 years, because usually architecture nightmare blows up in a longer term, not 1 year.

PS. Im pretty sure 10 small spaghetti apps will be worse to maintain than 1 spaghetti app, but what do i know ;)

Thread Thread
jsalinas11 profile image
Jordan

I guess I don't see your point. You're just staying an opinion, which is fine, but it seems baseless. You're saying a microfrontends is more complex than a monolith. I disagree. Having done both I'd say microapps are much easier to develop and maintain. Pulling them together isn't very hard either. Have you used single spa?

Thread Thread
pavelloz profile image
Paweł Kowalski

This sums it up well.

arch

If dev dont know how to write code, dev will make 💩 in any architecture.
The complexity on top of micro* will create additional mess that will be harder to handle.

Problems with architecture are long-term and surface after some team rotation, legacy code creation, test neglecting, etc. But you have some years until then, so dont worry ahead of time ;-)

Thread Thread
jsalinas11 profile image
Jordan

So your argument is that bad devs write bad code? ... Alright well I'm gonna bow out of this one. Unless you have a more substantive argument.

Collapse
fasani profile image
Michael Fasani

Can you elaborate more on how you split your frontends, just high level, do you do it by feature or by some other method?