The problem with micro frontends is that it doesnt solve the team scaling and introduces much more problems than it solves. Microservices are introduced on the backend mainly, because different systems behave differently. A frontend scales exactly for the same reasons so no need for micro frontends. A much better way is to create packages and scale along responsibilities. For example, it makes sense to have a design system team and a package to integrate them into the main project. Same for api communication, security etc
I think that the solution for the problem is using feature flags to avoid some of the work in progress to interfere with the deployment cycle. So two teams can work on the same code base.
@@christian.mar.garcia feature flags can also get complicated if there's lack of communication, and also sometimes you may end up with multiple feature flags that needs to be aware of each other
A quick hands on will be excelent thanks for this is very helpfull or a course if you have one please post it. An full integration video of all this techs can be really helpfull.
Спасибо! Меня на собеседовании спросили про микрофронтенд и я был в растерянности. Хотя я до сих пор не понимаю, зачем мне знать такое как энтри-левел разработчику
How can I, as a beginner in Frontend Development, create projects that will help me apply for a job as a junior Frontend Developer? I have been solving many challenges on Frontend Mentor, but is this enough?
I’d suggest working on a project that you yourself are deeply intereted in. Just make sure the project is 1) more or less useful for you/public, 2) is well designed and coded (and documented) 3) are worthy of showcasing it to your interviewers
I’d suggest working on a project that you yourself are deeply intereted in. Just make sure the project is 1) more or less useful for you/public, 2) is well designed and coded (and documented) 3) are worthy of showcasing it to your interviewers
Good question. The answer is - they can, but a more common approach is “Module Federation”, which is something that many libraries such as Webpack can do. What it does under the hood is - it dynamically loads code from another application at runtime and injects it into the page.
Don't know why micro frontend is even a thing. What problem it is solving and at what cost? It looked like it adds more problems rather than solving it
The problem with micro frontends is that it doesnt solve the team scaling and introduces much more problems than it solves. Microservices are introduced on the backend mainly, because different systems behave differently. A frontend scales exactly for the same reasons so no need for micro frontends.
A much better way is to create packages and scale along responsibilities. For example, it makes sense to have a design system team and a package to integrate them into the main project. Same for api communication, security etc
I think that the solution for the problem is using feature flags to avoid some of the work in progress to interfere with the deployment cycle. So two teams can work on the same code base.
@@christian.mar.garcia feature flags can also get complicated if there's lack of communication, and also sometimes you may end up with multiple feature flags that needs to be aware of each other
Yes. What you said is right. Micro frontend will create complexity to the system. Using packages is one of the best solution nowadays.
I am a new UI Developer and wondered about scalability on front end teams works. This was amazing and informative! Thank you!!
Glad you found it helpful! 🤓
wow! one of the best educators, please keep making more architectural videos, can you also focus on FE as well
Thanks a lot for the nice words and the feedback! Yes, I’ll do so 😛
starts at 3:29
A quick hands on will be excelent thanks for this is very helpfull or a course if you have one please post it. An full integration video of all this techs can be really helpfull.
Waiting for your microservices video!
Coming soon! 😊
You can deal with the deployment issues with feature flips
would be nice to see an example with authentication session.
I found this similar to monorepos by Nx or turborepo , but i don't know how to scale them seperatly
is MFe still relevant with Nextjs stack ?
Спасибо! Меня на собеседовании спросили про микрофронтенд и я был в растерянности. Хотя я до сих пор не понимаю, зачем мне знать такое как энтри-левел разработчику
Наверное это у них в стэке 🧐
How can I, as a beginner in Frontend Development, create projects that will help me apply for a job as a junior Frontend Developer? I have been solving many challenges on Frontend Mentor, but is this enough?
I’d suggest working on a project that you yourself are deeply intereted in. Just make sure the project is 1) more or less useful for you/public, 2) is well designed and coded (and documented) 3) are worthy of showcasing it to your interviewers
I’d suggest working on a project that you yourself are deeply intereted in. Just make sure the project is 1) more or less useful for you/public, 2) is well designed and coded (and documented) 3) are worthy of showcasing it to your interviewers
BTW micro frontends are damn more costly
Do microfrontends use s?
Good question. The answer is - they can, but a more common approach is “Module Federation”, which is something that many libraries such as Webpack can do. What it does under the hood is - it dynamically loads code from another application at runtime and injects it into the page.
@@SoftwareDeveloperDiaries in that case, would it need to all use the same framework like React or can you do it with React and Vue?
@@PeaceBeginsOnYourPlate they don't have to be same
Vercel to me do the best job with scaling
Don't know why micro frontend is even a thing. What problem it is solving and at what cost? It looked like it adds more problems rather than solving it
no example, vague solution, waste of time
Will try to improve this, thanks for the feedback!
Clearly this video is just covering theory, add "tutorial" to your search next time, crybaby