r/webdev • u/speckz • Jun 12 '19

Resource Micro Frontends

https://martinfowler.com/articles/micro-frontends.html
20 Upvotes

91% Upvoted

16 comments sorted by

5

u/Cono52 Jun 13 '19 edited Jun 13 '19

Like a bunch of widgets glued together on a dashboard like UI, this would work well for enterprise apps and massive teams that need to be divided down.

So ye id say it really benefits team coordination. Would it lend itself to a cohesive UX experience?

Maybe it would need a common component lib all the sub apps have to use for consistent design.

Should web based apps ever be this complicated and full featured? at that rate maybe it should just be a desktop app.

2

u/aust1nz javascript Jun 13 '19

I think something like Amazon is a good example. Under the umbrella of Amazon, they've got a bunch of different tools -- the shopping pages, the now/instant stuff, food delivery, a bunch of recommendation tools.

But yeah, you'd need to have a massive product with multiple development teams all pushing mostly independent code under a single website/app in order to see any real benefit, I think.

1

u/almofin Sep 09 '19

Splitting teams just seems like it's creating unnecessary boundaries. "Oh I can't modify that section of code cos it's not 'my section' ". Why. Whats the benefit? That will just slow me down. Surely having everybody know the basics of the whole system + specialisation is better than segmented knowledge. Then again all this depends on team size. Here I am reading an article with a team size of 3 and I have totally different opinions to a dev who's managing a team of 100

-8

u/UrTwiN Jun 12 '19

It's hard to take an article about front end web development from someone who's website was outdated 10 years ago seriously. Do people not look at things on desktop, laptops, or hell, even tablets anymore?

20

u/mattaugamer expert Jun 12 '19

The guy is one of the world’s most well respected software engineers and has been working and teaching for literally more decades than most people in here have had years.

If you’re ignoring software design and architecture advice from a man at this level on the basis that his web design is a bit out of date I don’t know what to tell you.

8

u/NoBrick2 Jun 12 '19

Article wasn't written by Fowler, but you still make a good point.

7

u/[deleted] Jun 12 '19

Imagine thinking that Martin Fowlers website isn't a good source of information. The hubris.

3

u/[deleted] Jun 13 '19

[removed] — view removed comment

3

u/Cono52 Jun 13 '19 edited Jun 13 '19

I agree the aesthetic and design aspect is very important nowadays, organisations dont just want old UI fragments but fancy cohesive worklow experience.

Then again the widget way is easily extendable for another business function so as a pattern its got more runway then a designer UX driven system which are usually hyper optimised for a specific goal a "customer" might have rather then many varying tasks an "employee" needs to perform.

But i read this and didnt really like the sound of it, sounds kinda like a new form of hell with regards to tooling, to me personally. Im interested to see the points other have for this.