#microfrontends — Public Fediverse posts

Excited for #JCON EUROPE 2026? See Lofi Dewanto & Patricia Erdelen at #JCON2026 in Cologne talking about '#Microservices and #Microfrontends: Scaling, Learning, Growing – Our #Journey'

Five years ago, our sales applications faced the …

🎟️ 2026.europe.jcon.one/tickets
Free for #JUG members

Interested in #Microfrontends? I'll be chatting with @manfredsteyer.bsky.social tomorrow about how we're tackling them at #Google and #Angular. We hope you'll stop by!

https://www.meetup.com/angular-meetup-graz/events/312845056/

🚀 𝐓𝐡𝐞 𝐁𝐞𝐬𝐭 𝐨𝐟 #𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐢𝐧 𝟐𝟎𝟐𝟓

Looking to stay ahead of the curve? Explore this 𝐦𝐮𝐬𝐭-𝐫𝐞𝐚𝐝 𝐜𝐨𝐥𝐥𝐞𝐜𝐭𝐢𝐨𝐧 𝐨𝐟 𝐬𝐭𝐚𝐧𝐝𝐨𝐮𝐭 𝐚𝐫𝐭𝐢𝐜𝐥𝐞𝐬 published on #InfoQ last year:

➡️ Agentic AI Architecture Framework for Enterprises by Subash Natarajan & Ahilan Ponnusamy
https://bit.ly/3IsMNi2

➡️ The End of the Bronze Age: Rethinking the Medallion Architecture by Adam Bellemare
https://bit.ly/3WHjxsf

➡️ Three Questions That Help You Build a Better Software Architecture by Pierre Pureur & Kurt Bittner
https://bit.ly/3L5Kdjk

➡️ Applying Flow Metrics to Design Resilient Microservices by Mourjo Sen
https://bit.ly/49lGMip

➡️ Micro-Frontends: a Sociotechnical Journey toward a Modern Frontend Architecture by Luca Mezzalira
https://bit.ly/4rC6iHl

📚 Stay informed. Stay inspired. And always #StayAhead of the curve - 𝐊𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 𝐢𝐬 𝐩𝐨𝐰𝐞𝐫 💪

#AgenticAI #SoftwareDesign #MedallionArchitecture #FlowMetrics #Microservices #MicroFrontends

Why Developers Are Ditching Frameworks for Vanilla JavaScript, by @TheNewStack:

https://thenewstack.io/why-developers-are-ditching-frameworks-for-vanilla-javascript/

#frameworks #javascript #apis #performance #microfrontends #architecture

Module Federation на примере фишинга

Разберём микрофронтенд через историю вымышленного хакера — и заодно поймём, почему это спрашивают на собеседованиях. Недавно на собесе меня спросили: "А как именно работают микрофронты? Там что, прямо eval используют?" Я что-то промямлил про expose, host, сборку... и понял, что вообще не понимаю сути. Знакомо?

https://habr.com/ru/articles/979242/

#microfrontends #микрофронтенды #вебпак #webpack #module_federation

How Microfrontends Work: 3 Integration Strategies, by (not on Mastodon or Bluesky):

https://www.sitepoint.com/microfrontends-integration/

#microfrontends #strategies #routing #iframes #javascript #ai

Von Abhängigkeits-Deadlocks bis zu Plugin-Freiheit – Christian Siebmanns‘ Reise zur #ModuleFederation ist ein Überlebenshandbuch für alle, die Legacy-Frontends modernisieren.

Lese vor deiner nächsten Migration: https://javapro.io/de/microfrontends-mit-module-federation-fuer-bestehende-anwendungen-ein-erfahrungsbericht/

#MicroFrontends #TypeScript #WebDevelopment

#SoftwareArchitects constantly navigate the tensions between Ideal & Pragmatic, Innovation & Stability, Speed & Safety.

This #InfoQ eMag offers perspectives to help you see your own challenges more clearly, along with patterns others have used successfully.

Most importantly, it’s a reminder that the best architectures emerge when we stop pretending technology exists separately from the humans who build & use it.

⬇️ Free download: https://bit.ly/48AMLhv

#SoftwareArchitecture #ArchitectureDecisionRecords #EventDrivenArchitecture #MicroFrontends #TechLeadership

#MicroFrontends reflect how modern organisations build software!

They signal a shift from:
🔹 Centralized Control ⇨ Distributed Ownership
🔹 Significant Releases ⇨ Continuous Flow
🔹 Rigid Architectures ⇨ Evolutionary Change

By migrating iteratively, you can modernise your frontend without slowing innovation.

📰 Read the #InfoQ article by Luca Mezzalira for more: https://bit.ly/4rC6iHl

#SoftwareArchitecture #SociotechnicalArchitecture

Микрофронтенды: прихоть разработчиков или реальная польза для бизнеса

История о том, как наша команда смогла ускорить релизы, снизить затраты и построить масштабируемую архитектуру без хаоса. В статье вы узнаете, подходят ли вам микрофронтенды.

https://habr.com/ru/articles/968994/

#frontend #microfrontends #architecture #javascript #reactjs #фронтенд #микрофронтенды #монолит #архитектура

What if a single missing #TypeScript spec blocks your entire frontend build? Christian Siebmanns uses #OpenAPI, Nexus, & Module Federation to solve real-world CI chain reactions.

A pragmatic, technical case study: https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/

#MicroFrontends #CI_CD #JAVAPRO #Webpack

🎥 In this #InfoQ video, Luca Mezzalira (Principal Solutions Architect, AWS) dives into the challenges, strategies & best practices for implementing #MicroFrontends effectively.

Discover the key architectural decisions behind successful implementations - and why a Platform Team and strong Developer Experience are essential.

👉 Watch now: https://bit.ly/47pZSBH

#SoftwareArchitecture #transcript included

#ModuleFederation ist nicht nur für Greenfield-Projekte. Christian Siebmanns führt Sie durch die Implementierung in eine ausgereifte App – mit Infos zu Shared Deps, dynamischem Laden & Version 2.

Lese: https://javapro.io/de/microfrontends-mit-module-federation-fuer-bestehende-anwendungen-ein-erfahrungsbericht/

#MicroFrontends #Webpack #TypeScript #WebDevelopment

Как просто использовать SRI, когда у тебя микрофронты

И чтобы всё было безопасно.

https://habr.com/ru/companies/alfa/articles/940324/

#cdn #infra #microfrontends #микрофронтенды #module_federation

How to Build Microfrontends With Module Federation and Vue, by @alexvue.bsky.social:

https://alexop.dev/posts/how-to-build-microfrontends-with-module-federation-and-vue/

#howtos #microfrontends #modules #vuejs

You’ve heard #MicroFrontends are flexible. But what happens when a plugin fails on page reload? Christian Siebmanns shows how even perfect webpack setups can collapse under real-world constraints.

A must-read for frontend architects: https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/

#ModuleFederation

Ihre App ist schon seit Jahren live – zu spät für #MicroFrontends? Christian Siebmanns beweist das Gegenteil. Von komplexen Abhängigkeiten zu klaren Plugin-Grenzen.

Lese die wichtigsten Praxis-Learnings: https://javapro.io/de/microfrontends-mit-module-federation-fuer-bestehende-anwendungen-ein-erfahrungsbericht/

#ModuleFederation #TypeScript #WebDevelopment

Dive into the evolution of #Microfrontends with Luca Mezzalira!

Discover key heuristics that will allow you to gradually implement them in your product and gain strategies to obtain quick feedback in your inner & outer development loops.

🎧 Listen to the #InfoQ #podcast: https://bit.ly/45rOJPT

📄 #transcript included

#SoftwareArchitecture #UserExperience #DistributedSystems

Microfrontends in ein bestehendes System integrieren – ohne dass Builds, Releases und Abhängigkeiten kollidieren.
Der Artikel zeigt, welche Architektur- und CI-Strategien funktionieren und welche Fehler man nur einmal machen möchte.
https://javapro.io/de/microfrontends-mit-module-federation-fuer-bestehende-anwendungen-ein-erfahrungsbericht/

#MicroFrontends #ModuleFederation #Webpack #TypeScript #WebDevelopment

Electron + microfrontends

Недавно на проекте столкнулся с необычной задачей - сделать из готового React веб-приложения десктопную версию на Electron. Что же тут необычного? А то, что наше веб-приложение построено на микрофронтенд архитектуре и располагается в трёх отдельных репозиториях. А общение между микрофронтендами происходит в runtime через HTTP. И тут начинаются сложности, так как для создания дистрибутива, Electron'у нужен доступ к исходникам всего приложения. Хотя Electron легко подружить с Webpack , как это сделать с плагином Module Federation на первый взгляд не понятно. Поиск готового решения в интернете ничего не дал, кроме повисших в воздухе вопросов на Stack Overflow. Пришлось придумать своё решение, которое я и опишу здесь. Стек проекта типовой (React, Webpack Module Federation, Electron, Electron-forge), поэтому не буду подробно расписывать конфиги, лишь опишу ключевые моменты.

https://habr.com/ru/articles/934068/

#webpack #electron #module_federation #microfrontends

90% legacy, 10% hope: Christian Siebmanns shares how his team retrofitted Module Federation into an existing app—without breaking everything. Lessons in builds, plugins & CI chaos: https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/

#MicroFrontends #ModuleFederation #Webpack #TypeScript #WebDevelopment

Tried to plug Module Federation into a running app? Christian Siebmanns shows what really happens when CI breaks, types vanish, & lazy routes fail. Learn how to avoid the same traps: https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/

#MicroFrontends #ModuleFederation #Webpack #TypeScript #WebDevelopment

#Decentralized #Module #Federation #Microfrontend #Architecture

I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

How it will be #architected: [https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)
Some #benefits of the #approach: [https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)

I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

#Cryptography modules - https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs

#P2P framework - https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs

This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

#P2P chat - [https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)
#P2P file transfer - [https://file.positive-intentions.com/](https://file.positive-intentions.com/)

The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

#Decentralized #Module #Federation #Microfrontend #Architecture

I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

How it will be #architected: [https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)
Some #benefits of the #approach: [https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)

I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

#Cryptography modules - https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs

#P2P framework - https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs

This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

#P2P chat - [https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)
#P2P file transfer - [https://file.positive-intentions.com/](https://file.positive-intentions.com/)

The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

#Decentralized #Module #Federation #Microfrontend #Architecture

I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

How it will be #architected: [https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)
Some #benefits of the #approach: [https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)

I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

#Cryptography modules - https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs

#P2P framework - https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs

This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

#P2P chat - [https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)
#P2P file transfer - [https://file.positive-intentions.com/](https://file.positive-intentions.com/)

The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

#Decentralized #Module #Federation #Microfrontend #Architecture

I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

How it will be #architected: [https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)
Some #benefits of the #approach: [https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)

I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

#Cryptography modules - https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs

#P2P framework - https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs

This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

#P2P chat - [https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)
#P2P file transfer - [https://file.positive-intentions.com/](https://file.positive-intentions.com/)

The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

#Decentralized #Module #Federation #Microfrontend #Architecture

I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

How it will be #architected: [https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)
Some #benefits of the #approach: [https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)

I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

#Cryptography modules - https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs

#P2P framework - https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs

This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

#P2P chat - [https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)
#P2P file transfer - [https://file.positive-intentions.com/](https://file.positive-intentions.com/)

The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

Micro-Frontend Architecture Pitfalls: Solving Integration and Deployment Challenges at Scale, by @designerly.bsky.social:

https://frontenddogma.com/posts/2025/micro-frontend-architecture-pitfalls/

#guestposts #microfrontends #architecture #scalability #deploying

Как мы распилили монолит на микрофронтенды с Vite и не сошли с ума

Наш фронтенд начинался как простой SPA на React, собранный с помощью Vite — типичный монолит с несколькими страницами. Со временем проект оброс новыми функциями и интеграциями и начал становиться всё сложнее в поддержке. На горизонте появились новые вызовы: к продукту планировалось подключать всё больше независимых сервисов, а значит — ещё больше интеграций и роста кодовой базы. Мы понимали, что нагрузка на инфраструктуру будет только увеличиваться, поэтому решили заранее заложить архитектуру с расчётом на масштабирование. После изучения разных вариантов мы остановились на подходе микрофронтендов. Хотелось разграничить зоны ответственности между командами и ускорить разработку, не теряя гибкости. В качестве сборщика решили остаться на Vite — он быстро развивался, предлагал отличную DX и поддержку модульной федерации через плагин. Кроме того, важно было сохранить единый репозиторий, чтобы упростить CI/CD и управление зависимостями.

https://habr.com/ru/companies/beeline_tech/articles/918860/

#микрофронтенды #vite #frontops #module_federation #microfrontends #react

От Lerna до ModuleFederation

Привет, Хабр! Меня зовут Дмитрий Ханин, я работаю в Сбере и участвую в разработке Платформы ЦА — системы на базе блокчейн, занимающейся привлечением средств юридических и физических лиц. Сегодня хотелось бы рассказать про тот путь, который мы прошли за несколько лет, как организовали взаимодействие между разными приложениями и чем нам это помогло. Рассказ разделён на две части. В первой рассмотрим путь проекта и проблемы, с которыми сталкивались, а во второй разберём, как мы решали часть этих проблем.

https://habr.com/ru/companies/sberbank/articles/911748/

#module_federation #webpack #microfrontends #опыт_разработчика

The Case for Web Components With Lit, by (unattributable):

https://typescript.guru/the-case-for-web-components-with-lit/

#webcomponents #lit #typescript #microfrontends

Mastering Cross-Framework State Management in Micro-Frontends, by @[email protected] (@[email protected]):

https://frontenddogma.com/posts/2025/mastering-cross-framework-state-management-in-micro-frontends/

#guestposts #architecture #frameworks #statemanagement #microfrontends #scaling #strategies

Passionate about Software Architecture?

✍️ Join the #InfoQ Annual Article Writing Competition and share your insights!

🏆 Win a #FreeTicket to #QCon or #InfoQDevSummit!

🔗 Submit by March 30, 2025: https://bit.ly/417KPtk

Explore topics like #CellBasedArchitecture, #GraphQLFederation, #DataDrivenArchitecture, #PlatformArchitecture, #EdgeComputing, #MicroFrontends, #AsyncAPI, and more!

Passionate about Software Architecture?

✍️ Join the #InfoQ Annual Article Writing Competition and share your insights!

🏆 Win a #FreeTicket to #QCon or #InfoQDevSummit!

🔗 Submit by March 30, 2025: https://bit.ly/417KPtk

Explore topics like #CellBasedArchitecture, #GraphQLFederation, #DataDrivenArchitecture, #PlatformArchitecture, #EdgeComputing, #MicroFrontends, #AsyncAPI, and more!

Decentralized microfrontend architecture.

The app is architected in a unique way to investigate possibilities and potential.

https://positive-intentions.com/blog/decentralised-architecture

#Microfrontends #JavaScript #WebDevelopment #Frontend #ModuleFederation #DynamicRemotes #SelfHosting #DevExperience #Scalability #AWS #GitHubPages #CDN #OpenSource

Spotify squad 1: I'm going to put notifications at the bottom of the screen!

Spotify squad 2: I'm going to put navigation and other buttons at the bottom of the screen!

Spotify user: Oh no!

#microfrontend #microfrontends

Spotify squad 1: I'm going to put notifications at the bottom of the screen!

Spotify squad 2: I'm going to put navigation and other buttons at the bottom of the screen!

Spotify user: Oh no!

#microfrontend #microfrontends

Spotify squad 1: I'm going to put notifications at the bottom of the screen!

Spotify squad 2: I'm going to put navigation and other buttons at the bottom of the screen!

Spotify user: Oh no!

#microfrontend #microfrontends

Microfronends as a #decentralized alternative to #npm.

While i can smush everything into a #monoRepo, i wanted to explore the idea of using #Microfrontends as a kind-of self managed alternative to #npm.

Microfronends have been around for a while and i've come across many different approaches. I want to share how im using microfrontends in my project.

Im using #Webpack 5 #moduleFederation to create the #microfrontend. there are some interesting features that i dont think are being mentioned elsewhere:

- Dynamic Remotes: Modules can be loaded from various endpoints. We can use a custom function to ping different URLs and determine the fastest one for loading the required module.

- #Selfhosters can manage modules independently, enhancing control over updates and #security on #opensource projects.

- Development Experience: By using dynamic-remotes and running modules locally during development, it can speed up testing and iteration.

- Scalability: The approach allows for #CDN scaling with module deployments on multiple cloud providers. currently, my redundencies are on AWS S3 + github-pages... but i can see how this can be scaled to more cloud providers.

Im aiming for the architecture to look like the following. Let me know your thoughts on my approach and if its something you would consider for your project.

https://positive-intentions.com/blog/decentralised-architecture

https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure

#Microfrontends #JavaScript #WebDevelopment #Frontend #ModuleFederation #DynamicRemotes #SelfHosting #DevExperience #Scalability #AWS #GitHubPages #CDN #OpenSource

Microfronends as a #decentralized alternative to #npm.

While i can smush everything into a #monoRepo, i wanted to explore the idea of using #Microfrontends as a kind-of self managed alternative to #npm.

Microfronends have been around for a while and i've come across many different approaches. I want to share how im using microfrontends in my project.

Im using #Webpack 5 #moduleFederation to create the #microfrontend. there are some interesting features that i dont think are being mentioned elsewhere:

- Dynamic Remotes: Modules can be loaded from various endpoints. We can use a custom function to ping different URLs and determine the fastest one for loading the required module.

- #Selfhosters can manage modules independently, enhancing control over updates and #security on #opensource projects.

- Development Experience: By using dynamic-remotes and running modules locally during development, it can speed up testing and iteration.

- Scalability: The approach allows for #CDN scaling with module deployments on multiple cloud providers. currently, my redundencies are on AWS S3 + github-pages... but i can see how this can be scaled to more cloud providers.

Im aiming for the architecture to look like the following. Let me know your thoughts on my approach and if its something you would consider for your project.

https://positive-intentions.com/blog/decentralised-architecture

https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure

#Microfrontends #JavaScript #WebDevelopment #Frontend #ModuleFederation #DynamicRemotes #SelfHosting #DevExperience #Scalability #AWS #GitHubPages #CDN #OpenSource

Microfronends as a #decentralized alternative to #npm.

While i can smush everything into a #monoRepo, i wanted to explore the idea of using #Microfrontends as a kind-of self managed alternative to #npm.

Microfronends have been around for a while and i've come across many different approaches. I want to share how im using microfrontends in my project.

Im using #Webpack 5 #moduleFederation to create the #microfrontend. there are some interesting features that i dont think are being mentioned elsewhere:

- Dynamic Remotes: Modules can be loaded from various endpoints. We can use a custom function to ping different URLs and determine the fastest one for loading the required module.

- #Selfhosters can manage modules independently, enhancing control over updates and #security on #opensource projects.

- Development Experience: By using dynamic-remotes and running modules locally during development, it can speed up testing and iteration.

- Scalability: The approach allows for #CDN scaling with module deployments on multiple cloud providers. currently, my redundencies are on AWS S3 + github-pages... but i can see how this can be scaled to more cloud providers.

Im aiming for the architecture to look like the following. Let me know your thoughts on my approach and if its something you would consider for your project.

https://positive-intentions.com/blog/decentralised-architecture

https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure

#Microfrontends #JavaScript #WebDevelopment #Frontend #ModuleFederation #DynamicRemotes #SelfHosting #DevExperience #Scalability #AWS #GitHubPages #CDN #OpenSource

Microfronends as a #decentralized alternative to #npm.

While i can smush everything into a #monoRepo, i wanted to explore the idea of using #Microfrontends as a kind-of self managed alternative to #npm.

Microfronends have been around for a while and i've come across many different approaches. I want to share how im using microfrontends in my project.

Im using #Webpack 5 #moduleFederation to create the #microfrontend. there are some interesting features that i dont think are being mentioned elsewhere:

- Dynamic Remotes: Modules can be loaded from various endpoints. We can use a custom function to ping different URLs and determine the fastest one for loading the required module.

- #Selfhosters can manage modules independently, enhancing control over updates and #security on #opensource projects.

- Development Experience: By using dynamic-remotes and running modules locally during development, it can speed up testing and iteration.

- Scalability: The approach allows for #CDN scaling with module deployments on multiple cloud providers. currently, my redundencies are on AWS S3 + github-pages... but i can see how this can be scaled to more cloud providers.

Im aiming for the architecture to look like the following. Let me know your thoughts on my approach and if its something you would consider for your project.

https://positive-intentions.com/blog/decentralised-architecture

https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure

#Microfrontends #JavaScript #WebDevelopment #Frontend #ModuleFederation #DynamicRemotes #SelfHosting #DevExperience #Scalability #AWS #GitHubPages #CDN #OpenSource

Microfronends as a #decentralized alternative to #npm.

While i can smush everything into a #monoRepo, i wanted to explore the idea of using #Microfrontends as a kind-of self managed alternative to #npm.

Microfronends have been around for a while and i've come across many different approaches. I want to share how im using microfrontends in my project.

Im using #Webpack 5 #moduleFederation to create the #microfrontend. there are some interesting features that i dont think are being mentioned elsewhere:

- Dynamic Remotes: Modules can be loaded from various endpoints. We can use a custom function to ping different URLs and determine the fastest one for loading the required module.

- #Selfhosters can manage modules independently, enhancing control over updates and #security on #opensource projects.

- Development Experience: By using dynamic-remotes and running modules locally during development, it can speed up testing and iteration.

- Scalability: The approach allows for #CDN scaling with module deployments on multiple cloud providers. currently, my redundencies are on AWS S3 + github-pages... but i can see how this can be scaled to more cloud providers.

Im aiming for the architecture to look like the following. Let me know your thoughts on my approach and if its something you would consider for your project.

https://positive-intentions.com/blog/decentralised-architecture

https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure

#Microfrontends #JavaScript #WebDevelopment #Frontend #ModuleFederation #DynamicRemotes #SelfHosting #DevExperience #Scalability #AWS #GitHubPages #CDN #OpenSource

I've also added a new sample that shows how to bring support for Edge Side Includes to YARP...

#MicroFrontends #EdgeSideIncludes #ESI #YARP #AspNetCore

Demystifying the Evolution of Software Architecture

About the transition from monolithic architecture to frontend-backend separation, and then to microservices over- time.

The article also explores the potential of combining micro frontends with microservices for more flexible and scalable applications.

#SoftwareArchitecture #Micoservices #MicroFrontends #Monoliths #WebDevelopment

https://www.computer.org/publications/tech-news/trends/software-architecture-evolution

Symbiote.js VS LitElement

Мотивация разработчиков библиотек и фреймворков для фронтенда может быть разной. И если вы, являясь таким разработчиком, хотите работать не “в стол” а с расчетом на какое-то признание и пользу для индустрии, вы должны четко понимать, что именно и зачем вы делаете. Если вы хотите сэкономить пользователям пару килобайт трафика или пару миллисекунд отклика - вам будет очень тяжело доказать миру, что ради этого стоит выбрать именно ваше решение. Люди выберут размер комьюнити, богатую экосистему и крупного вендора. Ваш набор аргументов должен быть достаточно веским, чтобы обратить на себя внимание. Сейчас я попытаюсь доказать, что при наличии такого решения как LitElement от гиганта индустрии Google, имеет смысл посмотреть в сторону Symbiote.js .

https://habr.com/ru/articles/788766/

#webразработка #webпрограммирование #фронтенд #webcomponents #javascript #microfrontends #css #shadow_dom #html #фреймфорки

New Edition Alert! 📢 The latest "Let’s Make Cloud" newsletter is out now!

This issue covers:
- Implementing GitFlow with Amazon CodeCatalyst 💻
- Exploring the AMBERSQUID Cloud-Native Cryptojacking Operation ☁️
- Understanding authentication challenges in microfrontend environments 🌐

Link: https://letsmakecloud.beehiiv.com/p/issue-41

#LetsMakeCloud #CloudComputing #TechNews #CloudSecurity #WebDevelopment #AWS #GitFlow #AMBERSQUID #Microfrontends

Wondering about the differences between #Monoliths, #Monorepos & #MicroFrontEnds?

👀 Watch this #InfoQ talk by Ruben Casas on the evolution of frontend applications at scale.

Explore each approach’s pros & cons and choose the best tool to help you scale your applications: https://bit.ly/3EIBygj

#FrontendArchitecture #WebDevelopment

Question for people using #MicroFrontends and #Monorepos: What do your #integration tests look like?

The #Google model of monorepos always builds everything at HEAD, but doing so would not catch version skew issues that come with independent deployments. That implies that your integration tests _cannot_ just build and run everything at HEAD, you actually have to deploy each change individually to a staging environment and alert on failures.

That feels like a much more complex setup than I'm used to seeing for integration tests. Do people actually do this or is version skew a giant blind spot for microfrontend testing?