DEV Community

Cover image for Companies already using micro frontends and why
OpenSource for Webcrumbs

Posted on • Edited on

Companies already using micro frontends and why

Micro frontends have emerged as a contemporary architectural pattern, simplifying front-end development in larger projects by breaking them down into smaller, manageable pieces. Notable companies across diverse domains are leveraging this pattern to enhance their development workflow and product delivery. Here's a list of some companies and the rationale behind their adoption:

Companies Treading the Micro Frontends Path:

Why the Adoption:

Micro frontends stand as a testament to an evolving web development landscape valuing modularization, team autonomy, and continuous delivery. For more insights and to contribute to the discourse, check out the WebCrumbs repository.

GitHub logo webcrumbs-community / webcrumbs

Build, re(use) and share your own JavaScript plugins that effortlessly match your website's style. 🌟 Star to support our work!

We're super excited to announce that we're working on a major overhaul of the repository.
Right now, we're not accepting contributions, but this will change soon! πŸ‘€
Star the repository and sign up at webcrumbs.org to be the first to know when we launch



Webcrumbs Logo

Build, (re)use and share your own JavaScript plugins

Sign our newsletter Β Β Β Β  Join our Discord

Webcrumbs Screen








Vision



WebCrumbs aspires to be an industry-standard solution for modern web development, creating the first open ecosystem of plugins for the JavaScript community and related frameworks (like React, Nextjs, Vue, Svelte, and others). Whether you're a developer or not, you'll find it easy to create, manage, and extend your own websites with our intuitive admin panel and a rich ecosystem of plugins developed by the community.

Diagram







Your Support Matters



If you love what WebCrumbs is doing, consider starring us on GitHub. Your support is key to refining our product and growing our community. Star WebCrumbs on GitHub.





Star our repository









Help Us Grow




  • Star the repository: If you haven't yet (yes, you!), give us a…




Top comments (3)

Collapse
 
barrymichaeldoyle profile image
Barry Michael Doyle

We use it at SecuritEase as well and at the beginning of the year when I was job hunting after a retrenchment, I found quite a lot of other companies also using MFEs.

After having gone all with it over the last year I've really come to appreciate the benefits of using them!

Collapse
 
opensourcee profile image
OpenSource • Edited

Thanks for sharing, @barrymichaeldoyle !

I'd love to know the downsides too. I talked to some friends that told me their companies either abandoned it because it started getting too intertwined, or were spending a lot of time and effort implementing it. Seems like a cultural change together with the architectural change. Did you guys experienced something like this?

Collapse
 
barrymichaeldoyle profile image
Barry Michael Doyle

I think it is indeed a cultural change and you need all team members onboard. We've been fortunate to have started out as a relatively small team on the frontend and it's been working well having us all onboard.

I worked for a company a couple of years ago that tried to implement this and it didn't work because one guy set it up but didn't really get the rest of the team onboard with it so it ended up being quite messy and very quickly wasn't maintained.

I'd say the biggest downside is the architectural mindset that everyone needs to have to get the most out of it. A lot of people don't put effort into really digging into how it should work and then end up getting impatiently frustrated when they struggle to add the the existing architecture. At least that's what I experienced when first trying to embrace this. Once those hurdles are overcome then it becomes pretty smooth sailing!