Which role do the micro-frontends play here?

The scenario

We can imagine that we’re a media company which our main revenue comes from publishing articles about music, art and festival events. We’re a Ticketmaster affiliate and we earn money for referring traffic to Ticketmaster pages which are related to the content inside our pages.

Ticketmaster affiliate program.

The general points and constraints

The authoring workflow for our editors resides completely in WordPress and Gutenberg. We need to let them list upcoming events based on a term without changing their current workflow. The company has planned in its roadmap implement a Headless CMS approach. We need to implement the Ticketmaster view on WordPress and reuse it later in the new Frontend without rewrite any code. The team maintaining the CMS platform have grown a lot. We need to distribute the teams by domains.

The approach

We can use custom blocks in Gutenberg for enabling editors to list upcoming events inside an article or page. However, WordPress needs to know how to interact with the Ticketmaster API in order to gather the necessary data to render the view and we’ll need to rewrite that logic later when the new Frontend come up.

Micro-frontends enable us to distribute views as services, with this premise we can have an independent team being owners of the Ticketmaster micro-frontend which knows how to communicate with the Ticketmaster API in order to render and distribute their views.

The solution

Code here