I have a single project that’s divided into several single-page applications: two built with Angular, two with React, and one with Vue.js. An integrated server handles file delivery based on routing rules, and I want to share data between these apps with minimal database interference. This setup represents a micro frontend architecture. Any suggestions on managing inter-app communication effectively would be highly appreciated.
hey guys im trying a shared evnt bus with pubsub. it lets your apps talk without heavy db reads. even a small api push periodically to sync state shows promise. sometimes simple is better then over complicatin, ya know?
hey i dabbled with html5 postmessage between iframes. its a bit of an hack but lets diverse apps commnicate without heavy backend load. security is key though so make sure you check origins and tokens.
In my experience, a robust solution for micro frontend communication involves implementing a centralized state management service rather than relying solely on direct event buses. This service acts as a mediator between different parts of the system, allowing for a single source of truth and reducing the reliance on multiple database writes. I found this approach minimises data inconsistencies and simplifies debugging. It is essential to design with clear boundaries and ensure your communication protocol handles asynchronous events effectively to maintain a responsive front-end architecture.
hey all, have u tried websokets for realtime state sharing? ive been experimentng with it, seems neat but a bit device prone. how do u handle fallback when connections drop? any other cool ideas?