Ohhh - I am sure of one thing, this is over -engineering AND very complicated to achieve.
Let's imagine some corporation wants a chat Micro App
And a Blog Micro App.
So they want to create 2 independent App, isolated from each other.
Fine.
They got 2 team, one decide to use React Hooks architecture for the blog, and the other one decide to use recoil for the chat. Down the line, they also have another Micro frontend App written in vue - that handles Authentication.
Then down the line - once those 2 apps have been deployed, they realize they need to integrate the Blog App into the Chat App.
They need to integrate a Blog Snippet inside the chat app. It is business critical, and many customers wants that.
(Again - this is imaginary product AAA).
Then Team Chat goes to team Blog and ask them to share some code with them.
But they can't. One uses Hooks, the other one uses Recoil - And it isn't clean enough for Team Chat - so they end up rewritting their own Blog Snippet preview.
Further down the line, The URL rewriting policy got updated... Now blogs links should display: /blog/title/id instead of /blog/id.
The Blog team update their code, but blog chat team don't get notified about the change -> Bug.
Yes I believe this is over engineer - and it isn't easy (Actually it is VERY complicated - and extremelly hard to maintain ) to share state between 2 micro frontend App.
So if you are certain those 2 Apps will never ever share code and state between each other, then fine. Go for it. Those are not 2 micro frontend app,s those are 2 separate apps, and you might just write one in React, and one in Svelte.
2 comments
[ 2.1 ms ] story [ 14.0 ms ] threadLet's imagine some corporation wants a chat Micro App And a Blog Micro App. So they want to create 2 independent App, isolated from each other. Fine. They got 2 team, one decide to use React Hooks architecture for the blog, and the other one decide to use recoil for the chat. Down the line, they also have another Micro frontend App written in vue - that handles Authentication.
Then down the line - once those 2 apps have been deployed, they realize they need to integrate the Blog App into the Chat App. They need to integrate a Blog Snippet inside the chat app. It is business critical, and many customers wants that. (Again - this is imaginary product AAA).
Then Team Chat goes to team Blog and ask them to share some code with them. But they can't. One uses Hooks, the other one uses Recoil - And it isn't clean enough for Team Chat - so they end up rewritting their own Blog Snippet preview.
Further down the line, The URL rewriting policy got updated... Now blogs links should display: /blog/title/id instead of /blog/id.
The Blog team update their code, but blog chat team don't get notified about the change -> Bug.
Yes I believe this is over engineer - and it isn't easy (Actually it is VERY complicated - and extremelly hard to maintain ) to share state between 2 micro frontend App.
So if you are certain those 2 Apps will never ever share code and state between each other, then fine. Go for it. Those are not 2 micro frontend app,s those are 2 separate apps, and you might just write one in React, and one in Svelte.