Now I finally understand that microfrontend buzzword :)
The part about the integration of the microfrontends was especially enlightening.
Regarding the takeaways - for the last couple of years, we considered this split, but still stayed with a monolith frontend. The guidelines are a bit vague, I know it always depends on the company and si…
Now I finally understand that microfrontend buzzword :)
The part about the integration of the microfrontends was especially enlightening.
Regarding the takeaways - for the last couple of years, we considered this split, but still stayed with a monolith frontend. The guidelines are a bit vague, I know it always depends on the company and situtation, but I was thinking maybe there are rules of thumb.
Something like amount of lines in a project, or number of developers working on the same frontend.
Now I finally understand that microfrontend buzzword :)
The part about the integration of the microfrontends was especially enlightening.
Regarding the takeaways - for the last couple of years, we considered this split, but still stayed with a monolith frontend. The guidelines are a bit vague, I know it always depends on the company and situtation, but I was thinking maybe there are rules of thumb.
Something like amount of lines in a project, or number of developers working on the same frontend.
The generic guidelines applies for the team size: 3-8 members.
I don't "think" the number of lines is important because the Micro Frontend should be based on bounded context (vertical sub-domains).