Jump to content

Scaling Micro-Frontends With Orchestrators


Recommended Posts

Multi-divisional organizations and team-building web applications with distributed teams are adopting micro-frontend architectures for front-end development similar to microservices. Large enterprises are seeing massive value in shifting from sequential to parallel development by architecting web experiences as independent, re-deployable, micro-frontend components.

What Are Micro-Frontends?

Micro-frontends are frontend components packaged as a mini-app to deliver a functional capability and web experience to end users. Each micro-frontend is deployable on its own and comprises user interactions and events representing a set of logical use cases for a given ecosystem. Micro-frontends share standard building blocks in the form of design system elements and dependencies in the form of self-contained packaged libraries. Micro-frontends are modular and contribute to scaling development to build parallel web experiences within an ecosystem. From a high-level skeleton code standpoint, here is a simple Micro-frontend with its package.json reflecting dependencies or scripts consumed by the micro-frontend as below.

16438257.gif

View the full article

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...