Domain-Driven Frontends

Domain-Driven Frontends Overview

At its core, domain-driven frontends is about doing one thing well inside your Module Federation project. Once you understand the pattern, you can apply it consistently across features and teams.

Good domain-driven frontends pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

const { ModuleFederationPlugin } = require('webpack').container;

module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      name: 'shell',
      remotes: { catalog: 'catalog@http://localhost:3001/remoteEntry.js' },
      exposes: {},
      shared: { react: { singleton: true }, 'react-dom': { singleton: true } },
    }),
  ],
};

ModuleFederationPlugin configures which modules an app exposes, consumes, and shares.

Domain-Driven Frontends Example

new ModuleFederationPlugin({
  name: 'app',
  filename: 'remoteEntry.js',
  exposes: { './Widget': './src/Widget' },
  remotes: { other: 'other@http://host/remoteEntry.js' },
  shared: { react: { singleton: true } },
});

• Start from a minimal Domain-Driven Frontends example and grow it only as needed.
• Keep configuration explicit so Domain-Driven Frontends behaves the same in every environment.
• Name things clearly so teammates understand your Domain-Driven Frontends at a glance.
• Add tests around Domain-Driven Frontends early to lock in expected behaviour.

Module Federation Cheatsheet

Key Module Federation settings related to domain-driven frontends.

How Domain-Driven Frontends Works in Module Federation

Domain-Driven Frontends builds on Module Federation's ability to load code from another independently built and deployed application at runtime. Each app can be a host, a remote, or both.

ModuleFederationPlugin configures which modules an app exposes, consumes, and shares.

• Remotes expose modules through a remoteEntry.js manifest.
• Hosts declare remotes and import exposed modules dynamically.
• Shared dependencies are deduplicated, ideally as singletons.
• Each micro frontend builds and deploys on its own schedule.

Practical Guidance for Domain-Driven Frontends

In production, domain-driven frontends needs careful version management and graceful failure handling. Align shared dependency versions and always render a fallback when a remote cannot load.

Common Mistakes

• Copying domain-driven frontends snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up domain-driven frontends.
• Leaving domain-driven frontends untested, so regressions slip into production.
• Over-engineering domain-driven frontends before you actually need the extra flexibility.

Key Takeaways

• Domain-Driven Frontends is a core part of working effectively with Module Federation.
• Start small and keep domain-driven frontends focused on a single responsibility.
• Apply consistent patterns so domain-driven frontends scales across your project.
• Test and document domain-driven frontends to keep it maintainable over time.