# Faster Builds With Module Federation - Nx Synced: [[2023_11_30]] 6:03 AM Last Highlighted: [[2023_10_10]] Tags: [[explainer]] [[software]] ![rw-book-cover](https://nx.dev/images/open-graph/concepts-more-concepts-faster-builds-with-module-federation.jpg) ## Highlights [[2023_10_10]] [View Highlight](https://read.readwise.io/read/01hccam0smcj1pjmrgv57bebts) > Whether Module Federation makes sense for your team depends on the size of your application. Although Nx hides most of the complexity around Module Federation, it still comes with some downsides: > • Developers need to think about which remotes they are working on, since it is a waste of CPU and memory to run *all* remotes in development mode. In practice this may not be a problem if the teams are already divided by domain or feature. > • Increased orchestration since remotes are independent of each other, shared state may require the host application to coordinate it between remotes. For example, sharing Redux state across remotes is more complicated versus a SPA. > [ > ](https://nx.dev/concepts/more-concepts/faster-builds-with-module-federation#architectural-overview) > With Module Federation, a large application is split into: > 1. A single **Host** application that references external... > 2. **Remote** applications, which handle a single domain or feature.