Fosstodon

InfoQDive into the evolution of <a href="https://techhub.social/tags/Microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microfrontends</a> 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 <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoQ</a> <a href="https://techhub.social/tags/podcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#podcast</a>: <a href="https://bit.ly/45rOJPT" rel="nofollow noopener" translate="no" target="_blank">https://bit.ly/45rOJPT</a> 📄 <a href="https://techhub.social/tags/transcript" class="mention hashtag" rel="nofollow noopener" target="_blank">#transcript</a> included<a href="https://techhub.social/tags/SoftwareArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareArchitecture</a> <a href="https://techhub.social/tags/UserExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#UserExperience</a> <a href="https://techhub.social/tags/DistributedSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#DistributedSystems</a>

JAVAPROMicrofrontends 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. <a href="https://javapro.io/de/microfrontends-mit-module-federation-fuer-bestehende-anwendungen-ein-erfahrungsbericht/" rel="nofollow noopener" translate="no" target="_blank">https://javapro.io/de/microfrontends-mit-module-federation-fuer-bestehende-anwendungen-ein-erfahrungsbericht/</a><a href="https://mastodon.social/tags/MicroFrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicroFrontends</a> <a href="https://mastodon.social/tags/ModuleFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModuleFederation</a> <a href="https://mastodon.social/tags/Webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webpack</a> <a href="https://mastodon.social/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#TypeScript</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a>

HabrElectron + microfrontendsНедавно на проекте столкнулся с необычной задачей - сделать из готового React веб-приложения десктопную версию на Electron. Что же тут необычного? А то, что наше веб-приложение построено на микрофронтенд архитектуре и располагается в трёх отдельных репозиториях. А общение между микрофронтендами происходит в runtime через HTTP. И тут начинаются сложности, так как для создания дистрибутива, Electron'у нужен доступ к исходникам всего приложения. Хотя Electron легко подружить с Webpack , как это сделать с плагином Module Federation на первый взгляд не понятно. Поиск готового решения в интернете ничего не дал, кроме повисших в воздухе вопросов на Stack Overflow. Пришлось придумать своё решение, которое я и опишу здесь. Стек проекта типовой (React, Webpack Module Federation, Electron, Electron-forge), поэтому не буду подробно расписывать конфиги, лишь опишу ключевые моменты.<a href="https://habr.com/ru/articles/934068/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/articles/934068/</a><a href="https://zhub.link/tags/webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#webpack</a> <a href="https://zhub.link/tags/electron" class="mention hashtag" rel="nofollow noopener" target="_blank">#electron</a> <a href="https://zhub.link/tags/module_federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#module_federation</a> <a href="https://zhub.link/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a>

JAVAPRO90% 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: <a href="https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/" rel="nofollow noopener" translate="no" target="_blank">https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/</a><a href="https://mastodon.social/tags/MicroFrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicroFrontends</a> <a href="https://mastodon.social/tags/ModuleFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModuleFederation</a> <a href="https://mastodon.social/tags/Webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webpack</a> <a href="https://mastodon.social/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#TypeScript</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a>

JAVAPROTried 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: <a href="https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/" rel="nofollow noopener" translate="no" target="_blank">https://javapro.io/2025/07/24/integrating-micro-frontends-into-existing-applications-lessons-learned/</a><a href="https://mastodon.social/tags/MicroFrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicroFrontends</a> <a href="https://mastodon.social/tags/ModuleFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModuleFederation</a> <a href="https://mastodon.social/tags/Webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webpack</a> <a href="https://mastodon.social/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#TypeScript</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a>

xoron :verified:<a href="https://infosec.exchange/tags/Decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#Decentralized</a> <a href="https://infosec.exchange/tags/Module" class="mention hashtag" rel="nofollow noopener" target="_blank">#Module</a> <a href="https://infosec.exchange/tags/Federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Federation</a> <a href="https://infosec.exchange/tags/Microfrontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microfrontend</a> <a href="https://infosec.exchange/tags/Architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#Architecture</a> I'm working on a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapp</a> and I'm being <a href="https://infosec.exchange/tags/creative" class="mention hashtag" rel="nofollow noopener" target="_blank">#creative</a> on the <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#approach</a>. It might be considered <a href="https://infosec.exchange/tags/overcomplicated" class="mention hashtag" rel="nofollow noopener" target="_blank">#overcomplicated</a> (because it is), but I'm just trying something out. It's entirely possible this approach won't work <a href="https://infosec.exchange/tags/longterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#longterm</a>. I see it as there is <a href="https://infosec.exchange/tags/onewaytofindout" class="mention hashtag" rel="nofollow noopener" target="_blank">#onewaytofindout</a>. I don't recommend this approach. Just sharing what I'm trying/#investigating.How it will be <a href="https://infosec.exchange/tags/architected" class="mention hashtag" rel="nofollow noopener" target="_blank">#architected</a>: [<a href="https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)</a> Some <a href="https://infosec.exchange/tags/benefits" class="mention hashtag" rel="nofollow noopener" target="_blank">#benefits</a> of the <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#approach</a>: [<a href="https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)</a>I find that <a href="https://infosec.exchange/tags/modulefederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#modulefederation</a> and <a href="https://infosec.exchange/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> to generally be <a href="https://infosec.exchange/tags/discouraged" class="mention hashtag" rel="nofollow noopener" target="_blank">#discouraged</a> when I see posts, but I think it works for me in my <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#approach</a>. I'm <a href="https://infosec.exchange/tags/optimistic" class="mention hashtag" rel="nofollow noopener" target="_blank">#optimistic</a> about the approach and the <a href="https://infosec.exchange/tags/benefits" class="mention hashtag" rel="nofollow noopener" target="_blank">#benefits</a> and so I wanted to <a href="https://infosec.exchange/tags/share" class="mention hashtag" rel="nofollow noopener" target="_blank">#share</a> details.When I serve the <a href="https://infosec.exchange/tags/federatedmodules" class="mention hashtag" rel="nofollow noopener" target="_blank">#federatedmodules</a>, I can also host the <a href="https://infosec.exchange/tags/storybook" class="mention hashtag" rel="nofollow noopener" target="_blank">#storybook</a> statics so I think this could be a good way to <a href="https://infosec.exchange/tags/document" class="mention hashtag" rel="nofollow noopener" target="_blank">#document</a> the modules in <a href="https://infosec.exchange/tags/isolation" class="mention hashtag" rel="nofollow noopener" target="_blank">#isolation</a>.<a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cryptography</a> modules - <a href="https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs" rel="nofollow noopener" translate="no" target="_blank">https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs</a><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#P2P</a> framework - <a href="https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs" rel="nofollow noopener" translate="no" target="_blank">https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs</a>This way, I can create <a href="https://infosec.exchange/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> that consume these <a href="https://infosec.exchange/tags/modules" class="mention hashtag" rel="nofollow noopener" target="_blank">#modules</a>. I can then <a href="https://infosec.exchange/tags/share" class="mention hashtag" rel="nofollow noopener" target="_blank">#share</a> the <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#functionality</a> between <a href="https://infosec.exchange/tags/apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#apps</a>. The following apps are using a different codebase from each other (there is a <a href="https://infosec.exchange/tags/distinction" class="mention hashtag" rel="nofollow noopener" target="_blank">#distinction</a> between these apps in <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> and <a href="https://infosec.exchange/tags/closesource" class="mention hashtag" rel="nofollow noopener" target="_blank">#closesource</a>). Sharing those <a href="https://infosec.exchange/tags/dependencies" class="mention hashtag" rel="nofollow noopener" target="_blank">#dependencies</a> could help make it easier to roll out <a href="https://infosec.exchange/tags/updates" class="mention hashtag" rel="nofollow noopener" target="_blank">#updates</a> to <a href="https://infosec.exchange/tags/coremechanics" class="mention hashtag" rel="nofollow noopener" target="_blank">#coremechanics</a>.<a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#P2P</a> chat - [<a href="https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)" rel="nofollow noopener" translate="no" target="_blank">https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)</a> <a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#P2P</a> file transfer - [<a href="https://file.positive-intentions.com/](https://file.positive-intentions.com/)" rel="nofollow noopener" translate="no" target="_blank">https://file.positive-intentions.com/](https://file.positive-intentions.com/)</a>The <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#functionality</a> also works when I create an <a href="https://infosec.exchange/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> build with <a href="https://infosec.exchange/tags/Tauri" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tauri</a>. This could also lead to it being easier to create <a href="https://infosec.exchange/tags/newapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#newapps</a> that could use the <a href="https://infosec.exchange/tags/modules" class="mention hashtag" rel="nofollow noopener" target="_blank">#modules</a> created.I'm sure there will be some distinct <a href="https://infosec.exchange/tags/test" class="mention hashtag" rel="nofollow noopener" target="_blank">#test</a>/#maintenance <a href="https://infosec.exchange/tags/overhead" class="mention hashtag" rel="nofollow noopener" target="_blank">#overhead</a>, but depending on how it's <a href="https://infosec.exchange/tags/architected" class="mention hashtag" rel="nofollow noopener" target="_blank">#architected</a> I think it could work and make it easier to <a href="https://infosec.exchange/tags/improve" class="mention hashtag" rel="nofollow noopener" target="_blank">#improve</a> on the current <a href="https://infosec.exchange/tags/implementation" class="mention hashtag" rel="nofollow noopener" target="_blank">#implementation</a>.Everything about the <a href="https://infosec.exchange/tags/project" class="mention hashtag" rel="nofollow noopener" target="_blank">#project</a> is far from finished. It could be seen as this is a <a href="https://infosec.exchange/tags/complicated" class="mention hashtag" rel="nofollow noopener" target="_blank">#complicated</a> way to do what <a href="https://infosec.exchange/tags/npm" class="mention hashtag" rel="nofollow noopener" target="_blank">#npm</a> does, but I think this <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#approach</a> allows for greater <a href="https://infosec.exchange/tags/flexibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#flexibility</a> by being able to <a href="https://infosec.exchange/tags/separate" class="mention hashtag" rel="nofollow noopener" target="_blank">#separate</a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> and <a href="https://infosec.exchange/tags/closesource" class="mention hashtag" rel="nofollow noopener" target="_blank">#closesource</a> code for the <a href="https://infosec.exchange/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a>. (Of course as <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>, it will always be "source code available". Especially in the age of <a href="https://infosec.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>, I'm sure it's possible to <a href="https://infosec.exchange/tags/reverseengineer" class="mention hashtag" rel="nofollow noopener" target="_blank">#reverseengineer</a> 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.)

Frontend DogmaMicro-Frontend Architecture Pitfalls: Solving Integration and Deployment Challenges at Scale, by @designerly.bsky.social:<a href="https://frontenddogma.com/posts/2025/micro-frontend-architecture-pitfalls/" rel="nofollow noopener" translate="no" target="_blank">https://frontenddogma.com/posts/2025/micro-frontend-architecture-pitfalls/</a><a href="https://mas.to/tags/guestposts" class="mention hashtag" rel="nofollow noopener" target="_blank">#guestposts</a> <a href="https://mas.to/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> <a href="https://mas.to/tags/architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#architecture</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener" target="_blank">#scalability</a> <a href="https://mas.to/tags/deploying" class="mention hashtag" rel="nofollow noopener" target="_blank">#deploying</a>

HabrКак мы распилили монолит на микрофронтенды с Vite и не сошли с умаНаш фронтенд начинался как простой SPA на React, собранный с помощью Vite — типичный монолит с несколькими страницами. Со временем проект оброс новыми функциями и интеграциями и начал становиться всё сложнее в поддержке. На горизонте появились новые вызовы: к продукту планировалось подключать всё больше независимых сервисов, а значит — ещё больше интеграций и роста кодовой базы. Мы понимали, что нагрузка на инфраструктуру будет только увеличиваться, поэтому решили заранее заложить архитектуру с расчётом на масштабирование. После изучения разных вариантов мы остановились на подходе микрофронтендов. Хотелось разграничить зоны ответственности между командами и ускорить разработку, не теряя гибкости. В качестве сборщика решили остаться на Vite — он быстро развивался, предлагал отличную DX и поддержку модульной федерации через плагин. Кроме того, важно было сохранить единый репозиторий, чтобы упростить CI/CD и управление зависимостями.<a href="https://habr.com/ru/companies/beeline_tech/articles/918860/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/companies/beeline_tech/articles/918860/</a><a href="https://zhub.link/tags/%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%D1%84%D1%80%D0%BE%D0%BD%D1%82%D0%B5%D0%BD%D0%B4%D1%8B" class="mention hashtag" rel="nofollow noopener" target="_blank">#микрофронтенды</a> <a href="https://zhub.link/tags/vite" class="mention hashtag" rel="nofollow noopener" target="_blank">#vite</a> <a href="https://zhub.link/tags/frontops" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontops</a> <a href="https://zhub.link/tags/module_federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#module_federation</a> <a href="https://zhub.link/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> <a href="https://zhub.link/tags/react" class="mention hashtag" rel="nofollow noopener" target="_blank">#react</a>

HabrОт Lerna до ModuleFederationПривет, Хабр! Меня зовут Дмитрий Ханин, я работаю в Сбере и участвую в разработке Платформы ЦА — системы на базе блокчейн, занимающейся привлечением средств юридических и физических лиц. Сегодня хотелось бы рассказать про тот путь, который мы прошли за несколько лет, как организовали взаимодействие между разными приложениями и чем нам это помогло. Рассказ разделён на две части. В первой рассмотрим путь проекта и проблемы, с которыми сталкивались, а во второй разберём, как мы решали часть этих проблем.<a href="https://habr.com/ru/companies/sberbank/articles/911748/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/companies/sberbank/articles/911748/</a><a href="https://zhub.link/tags/module_federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#module_federation</a> <a href="https://zhub.link/tags/webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#webpack</a> <a href="https://zhub.link/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> <a href="https://zhub.link/tags/%D0%BE%D0%BF%D1%8B%D1%82_%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%87%D0%B8%D0%BA%D0%B0" class="mention hashtag" rel="nofollow noopener" target="_blank">#опыт_разработчика</a>

Frontend DogmaThe Case for Web Components With Lit, by (unattributable):<a href="https://typescript.guru/the-case-for-web-components-with-lit/" rel="nofollow noopener" translate="no" target="_blank">https://typescript.guru/the-case-for-web-components-with-lit/</a><a href="https://mas.to/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a> <a href="https://mas.to/tags/lit" class="mention hashtag" rel="nofollow noopener" target="_blank">#lit</a> <a href="https://mas.to/tags/typescript" class="mention hashtag" rel="nofollow noopener" target="_blank">#typescript</a> <a href="https://mas.to/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a>

Frontend DogmaMastering Cross-Framework State Management in Micro-Frontends, by @eleanorhecks@x.com (@designerlymag@x.com):<a href="https://frontenddogma.com/posts/2025/mastering-cross-framework-state-management-in-micro-frontends/" rel="nofollow noopener" translate="no" target="_blank">https://frontenddogma.com/posts/2025/mastering-cross-framework-state-management-in-micro-frontends/</a><a href="https://mas.to/tags/guestposts" class="mention hashtag" rel="nofollow noopener" target="_blank">#guestposts</a> <a href="https://mas.to/tags/architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#architecture</a> <a href="https://mas.to/tags/frameworks" class="mention hashtag" rel="nofollow noopener" target="_blank">#frameworks</a> <a href="https://mas.to/tags/statemanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#statemanagement</a> <a href="https://mas.to/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> <a href="https://mas.to/tags/scaling" class="mention hashtag" rel="nofollow noopener" target="_blank">#scaling</a> <a href="https://mas.to/tags/strategies" class="mention hashtag" rel="nofollow noopener" target="_blank">#strategies</a>

InfoQPassionate about Software Architecture? ✍️ Join the <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoQ</a> Annual Article Writing Competition and share your insights! 🏆 Win a <a href="https://techhub.social/tags/FreeTicket" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeTicket</a> to <a href="https://techhub.social/tags/QCon" class="mention hashtag" rel="nofollow noopener" target="_blank">#QCon</a> or <a href="https://techhub.social/tags/InfoQDevSummit" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoQDevSummit</a>!🔗 Submit by March 30, 2025: <a href="https://bit.ly/417KPtk" rel="nofollow noopener" translate="no" target="_blank">https://bit.ly/417KPtk</a> Explore topics like <a href="https://techhub.social/tags/CellBasedArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#CellBasedArchitecture</a>, <a href="https://techhub.social/tags/GraphQLFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#GraphQLFederation</a>, <a href="https://techhub.social/tags/DataDrivenArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataDrivenArchitecture</a>, <a href="https://techhub.social/tags/PlatformArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#PlatformArchitecture</a>, <a href="https://techhub.social/tags/EdgeComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#EdgeComputing</a>, <a href="https://techhub.social/tags/MicroFrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicroFrontends</a>, <a href="https://techhub.social/tags/AsyncAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AsyncAPI</a>, and more!

QCon Software ConferencesPassionate about Software Architecture? ✍️ Join the <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoQ</a> Annual Article Writing Competition and share your insights! 🏆 Win a <a href="https://techhub.social/tags/FreeTicket" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeTicket</a> to <a href="https://techhub.social/tags/QCon" class="mention hashtag" rel="nofollow noopener" target="_blank">#QCon</a> or <a href="https://techhub.social/tags/InfoQDevSummit" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoQDevSummit</a>!🔗 Submit by March 30, 2025: <a href="https://bit.ly/4gKC51N" rel="nofollow noopener" translate="no" target="_blank">https://bit.ly/4gKC51N</a>Explore topics like <a href="https://techhub.social/tags/CellBasedArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#CellBasedArchitecture</a>, <a href="https://techhub.social/tags/GraphQLFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#GraphQLFederation</a>, <a href="https://techhub.social/tags/DataDrivenArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataDrivenArchitecture</a>, <a href="https://techhub.social/tags/PlatformArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#PlatformArchitecture</a>, <a href="https://techhub.social/tags/EdgeComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#EdgeComputing</a>, <a href="https://techhub.social/tags/MicroFrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicroFrontends</a>, <a href="https://techhub.social/tags/AsyncAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AsyncAPI</a>, <a href="https://techhub.social/tags/Dapr" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dapr</a>, <a href="https://techhub.social/tags/OpenTelemetry" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenTelemetry</a>, and more!

Roman VeselyThere are many articles describing micro frontends architecture, but most of them are about how to split one application into multiple parts. In our company we are facing opposite task - we are in the process of merging dozens of applications into the one. Which is an equally difficult problem to solve.<a href="https://mastodon.social/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a>

xoron :verified:Decentralized microfrontend architecture.The app is architected in a unique way to investigate possibilities and potential.<a href="https://positive-intentions.com/blog/decentralised-architecture" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/decentralised-architecture</a><a href="https://infosec.exchange/tags/Microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microfrontends</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/ModuleFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModuleFederation</a> <a href="https://infosec.exchange/tags/DynamicRemotes" class="mention hashtag" rel="nofollow noopener" target="_blank">#DynamicRemotes</a> <a href="https://infosec.exchange/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://infosec.exchange/tags/DevExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevExperience</a> <a href="https://infosec.exchange/tags/Scalability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scalability</a> <a href="https://infosec.exchange/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a> <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDN</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

jmsfbsSpotify 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!<a href="https://mastodon.social/tags/microfrontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontend</a> <a href="https://mastodon.social/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a>

Doug Parker 🕸️Probably 99% of the time, when I see someone asking about <a href="https://techhub.social/tags/Microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microfrontends</a> they go on to describe a use case which absolutely does *not* require microfrontends.MFEs are complicated, slow, and hard to maintain. They should almost always be your *last* resort to solving any particular problem.

Habr[Перевод] Micro Frontend ArchitectureВсем привет! На связи Spectr и новая рубрика «Что читают наши разработчики?». Сегодня делимся статьей о микрофронтенде. Почему мы выбрали эту тему? Микрофронтенды становятся всё более популярными в больших приложениях. С ростом числа распределенных команд и увеличением количества функций в современных продуктах архитектура микрофронтендов позволяет командам работать параллельно и автономно, внедряя новые функции без влияния на другие части системы. Этот подход помогает ускорить процесс разработки, уменьшить риски при развертывании и упрощает интеграцию различных технологий в одном проекте. Узнать о микрофронтенде больше<a href="https://habr.com/ru/companies/spectr/articles/856266/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/companies/spectr/articles/856266/</a><a href="https://zhub.link/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> <a href="https://zhub.link/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://zhub.link/tags/ecommerce" class="mention hashtag" rel="nofollow noopener" target="_blank">#ecommerce</a> <a href="https://zhub.link/tags/ecom" class="mention hashtag" rel="nofollow noopener" target="_blank">#ecom</a> <a href="https://zhub.link/tags/architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#architecture</a> <a href="https://zhub.link/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>

xoron :verified:Microfronends as a <a href="https://infosec.exchange/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralized</a> alternative to <a href="https://infosec.exchange/tags/npm" class="mention hashtag" rel="nofollow noopener" target="_blank">#npm</a>.While i can smush everything into a <a href="https://infosec.exchange/tags/monoRepo" class="mention hashtag" rel="nofollow noopener" target="_blank">#monoRepo</a>, i wanted to explore the idea of using <a href="https://infosec.exchange/tags/Microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microfrontends</a> as a kind-of self managed alternative to <a href="https://infosec.exchange/tags/npm" class="mention hashtag" rel="nofollow noopener" target="_blank">#npm</a>.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 <a href="https://infosec.exchange/tags/Webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webpack</a> 5 <a href="https://infosec.exchange/tags/moduleFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#moduleFederation</a> to create the <a href="https://infosec.exchange/tags/microfrontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontend</a>. 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.- <a href="https://infosec.exchange/tags/Selfhosters" class="mention hashtag" rel="nofollow noopener" target="_blank">#Selfhosters</a> can manage modules independently, enhancing control over updates and <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> on <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> 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 <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDN</a> 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.<a href="https://positive-intentions.com/blog/decentralised-architecture" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/decentralised-architecture</a><a href="https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure</a><a href="https://infosec.exchange/tags/Microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microfrontends</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/ModuleFederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModuleFederation</a> <a href="https://infosec.exchange/tags/DynamicRemotes" class="mention hashtag" rel="nofollow noopener" target="_blank">#DynamicRemotes</a> <a href="https://infosec.exchange/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://infosec.exchange/tags/DevExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevExperience</a> <a href="https://infosec.exchange/tags/Scalability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scalability</a> <a href="https://infosec.exchange/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a> <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDN</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

HabrПравильные ли у вас микрофронты?Как избежать типичные ошибки при внедрении микрофронтов и какие инструменты упрощают жизнь разработчикам. Рассмотрим плохие примеры разделение кода приложения, т.е. когда "архитектор" или лид проекта, не умеют микрофронты готовить. А разработчикам нужно с этим жить.<a href="https://habr.com/ru/articles/859230/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/articles/859230/</a><a href="https://zhub.link/tags/webpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#webpack</a> <a href="https://zhub.link/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#microfrontends</a> <a href="https://zhub.link/tags/react" class="mention hashtag" rel="nofollow noopener" target="_blank">#react</a>

Recent searches

Search options

Administered by:

Server stats:

#MicroFrontends