• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

Micro Frontends - When to Consider

Posts: 3205
Android Eclipse IDE TypeScript Redhat MicroProfile Quarkus Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Many of the projects that I am involved with start simple, and grow more complex over time.  When does it make sense to start thinking about a micro frontend architecture?  It seems like it would bring a lot of extra burden with little (or negative) gain if applied when project is small.
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would say that the decision whether to apply the micro frontend architecture should be taken from the beginning.
From what I see, micro-frontend involves the architecture of the project as a whole. So changing in a later stage from my traditional frontend approach to micro-frontend will cause to refactor a lot of things and this, in big project/team/company will need a whole set of regression testing, just for mentioning one.
But I think Michael Geers would have a better advice on this.
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, totally agreed. The architecture, similar to microservices, introduces overhead. I wouldn't recommend starting a new project with micro frontends unless you are pretty certain that you'll need the technical and organisational benefits this architecture can provide. It can make sense to adopt if from the start if you a) know that your project will grow quickly and b) it's easy for you to make good system boundary decisions early on because you know the domain very well.
I'm not sure if I approve of this interruption. But this tiny ad checks out:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic