This repository contains the source code of a simple micro frontends application written in Svelte and React.

• Micro frontends is similar thing on the frontend side, as microservices are on the backend side.
• Applications are composed of a set of well-defined, loosely coupled components.
• We can identify micro frontends in our applications by applying principles, such as Domain Driven Desing (DDD).
• Each micro frontend is owned by a single cross-functional team.
  • Easier scaling of teams and projects.
  • Smaller scope enables faster onboarding of new teams and team members.
• Teams can more freely pick their technology stack.
  • Prevents technology lock-in.
  • Makes applications more future-proof by allowing teams to more easily experiment with and migrate to new technologies.
• We get independent updates, so that if one part of the application changes, we only need to update the micro frontend(s) that implement the changed functionality.
• Micro frontends patterns can be very effective when migrating an existing monolithic application to a more modular architecture.
  • Strangler Pattern to kill the monolith by eating it piece-by-piece, until there is nothing left from the original implementation.
• Micro frontends is no silver bullet. It comes with its own challenges, such as operational and governance complexity, and possibly bigger payload sizes.
• The important thing is to understand the trade-offs, and make an informed decision on whether to adopt micro frontends in your applications.

There exist several approaches to implement micro frontends.

Decisions frameworks like the one presented here, can prove to be really useful in the early stages of a project.

Micro frontends continue to gain in popularity, so there already exist several libraries and frameworks to implement them.

• single-spa
• Frint
• Luigi

Custom solution is also a perfectly viable option. It gives you the full flexibility to innovate and evolve your solution.

The sample application in this repository is implemented without any 3rd party micro frontend libraries.

• https://martinfowler.com/articles/micro-frontends.html
• https://medium.com/@lucamezzalira
• https://medium.com/@lucamezzalira/micro-frontends-resources-53b1ec7d512a

• Gateway to the application.
• Implements the top menu and client-side routing.
• Loads (lazy), mounts, and unmounts micro frontends based on application state.
• Technologies: Svelte, Router5, Ky, Bootstrap, Vite

• Implements browse experience.
• Shows a list of selectable items.
• Technologies: React, Ky, Bootstrap, Vite

• Implements detail experience.
• Shows some details about the selected item.
• Technologies: Svelte, Ky, Bootstrap, Vite

• Provides JSON data and images for the application.

Application shell and the micro frontends use Bootstrap for styling.

Application shell and the micro frontends can communicate in a loosely coupled way by using the standard Custom Events API.

> docker compose up --build -d
> open http://localhost:8000