10 Comments
User's avatar
Basma Taha's avatar

Great break down of the topic.

I don't know much about frontend as I am a backend developer. But, learned a lot of new things from this!

Expand full comment
Neo Kim's avatar

thanks for the feedback, Basma.

Expand full comment
Vikas Kumar Yadav's avatar

I knew about Micro frontend however reading this makes things more concrete. Coincidently the question of micro frontend has been asked to me 2 times in different interviews after I read this. Thanks so much for this well written article :)

Expand full comment
Neo Kim's avatar

you're welcome, Vikas.

Expand full comment
Bernardo Gomes de Abreu's avatar

Great article!! Thanks for sharing !!

Expand full comment
Neo Kim's avatar

thank you for the feedback, Bernardo.

Expand full comment
hamza's avatar

how do i refer you to other people?

Expand full comment
Neo Kim's avatar

hey, use the share button in this post or get the link from https://newsletter.systemdesign.one/leaderboard

Expand full comment
Anton Zaides's avatar

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.

Expand full comment
Neo Kim's avatar

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).

Expand full comment