I HATE MICROFRONDENDS I HATE MICROFRONDENDS I HATE MICROFRONDENDS I HATE MICROFRONDENDS

Why microfrontends when you could have microfondues?

Hmmm, cheese

Microfrondedad

Microaggression...

What about microservices? Do you hate them too? Why /why not?

First time hearing this term. How micro does it get?

Like would a news site have entirely separate services for the front page and article pages? Or even more micro - one service for the article header html and a different one for the article body?

@jiraTicket I think the idea is that you architect your micro-frontends along organization lines, ex: 1 team develops a website frame in Symfony PHP, and they have layouts w. divs which load SPA apps by 1 or more other teams On different pages (I actually worked on such a team, but "microfrontends" was not a thing yet).

Evidently component level is too low-level

@webketje I see. Well it seems silly to have primary content in iframes. But for stuff like ads, checkout/payment flows, comment feeds etc it sounds like it makes a lot of sense if a company has 8 sites with 1 team each - to centralize some common festures that sre normally iframed, like ads.

But seems like a more obvious choice compared to microServices where it’s not just a choice based off team size necessity but more of an architecture decision

@jiraTicket it IS silly to have primary content in iframes. The SPA can be loaded in the <main> element or just a <div> for example and yes it shares the same CSS namespace (css modules & shadow roots ao. can eliminate potential clashes)

DigitalOcean's glob tool is a micro-frontend (https://github.com/do-community/...). You can develop it locally and embed it anywhere you want without the digitalocean.com nav frame, footer etc. It is deployed to Github Pages and dynamically loaded (via script & css tags) on their website