Angular

275 readers

2 users here now

A community for discussion about angular

Wormhole

[email protected]

Logo base by Angular under CC BY 4.0 with modifications to add a gradient and drop shadow

founded 1 year ago

MODERATORS

[email protected]

Micro frontends (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Does anyone have experience with breaking apart a large Angular frontend into micro frontends? Any advice you can offer or resources you can point me to would be greatly appreciated. Ideally I'd like to be able to mix Angular versions and different technologies (e.g. React) in the future as well, assuming that's possible.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago (1 children)

In a larger project we came up with the following solution, to keep the UI parts independent changeable and composable. For every bounded context there is an independent UI which could be used standalone and is versioned and exported as a Web Components. The main application provides the overall context and imports a certain major version (eg. "latest") of a of each component. All communication between the components is done by exchanging events and callbacks. It was in a vue-based project, but I think this should work in general as well.

[–] [email protected] 1 points 1 year ago

That's really interesting. We were looking at web components since the design team has been working on providing them to our customers. Thank you!