Even though I totally agree with every single point, in practice most of these are quite difficult to respect.
For example in the first one, when migrating a part of a system into a separate microfrontend, there is going to be a period (which in most cases is not that short) where both frontend are going to have a fairly tightly coupled.
What use cases have you experienced? Iām just thinking that all these points are a bit of ideal circumstances which are not that common in the development world. What do you think?
šØāš» Staff Engineer at Postman. š Conference Speaker. āļø Writing about Micro-Frontends and Frontend Architecture at Scale ā¤ļø We rise by lifting others.
Yeah, so they are more like guidelines that if you follow them you will unlock all the benefits of Micro-frontends and save you a lot of headaches. Regarding the migration one, I think that's the best time to sit down and design your application, avoiding coupling is probably the most important rule and there is usually a way forward to avoid it but requires a bit more work and being intentional about the decisions made early on in your Micro-Frontend journey.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Even though I totally agree with every single point, in practice most of these are quite difficult to respect.
For example in the first one, when migrating a part of a system into a separate microfrontend, there is going to be a period (which in most cases is not that short) where both frontend are going to have a fairly tightly coupled.
What use cases have you experienced? Iām just thinking that all these points are a bit of ideal circumstances which are not that common in the development world. What do you think?
Yeah, so they are more like guidelines that if you follow them you will unlock all the benefits of Micro-frontends and save you a lot of headaches. Regarding the migration one, I think that's the best time to sit down and design your application, avoiding coupling is probably the most important rule and there is usually a way forward to avoid it but requires a bit more work and being intentional about the decisions made early on in your Micro-Frontend journey.