Backend · NestJS · Design Patterns

NestFactory Is a Factory: How Nest.js Bootstraps from a Single create() Call

By dzhd · Aug 17, 2026

Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Understanding that NestFactory.create() is a factory — not just a bootstrap ritual — clarifies why Nest applications scale: the framework's module system and DI container are built on the same encapsulation principle that keeps call sites decoupled from implementation changes.

Summary

The factory pattern isn't just a textbook abstraction in Nest.js — it's the literal entry point. NestFactory.create() takes a root module and returns a fully wired application instance, hiding Express or Fastify configuration, middleware setup, and dependency resolution behind a single call. This mirrors the classic factory example where a consumer asks for a product by type and receives a ready-to-use instance without knowing construction details.

Inside that root module, the @Module decorator acts as a manifest, declaring which controllers handle routing, which providers contain business logic, and which external modules are needed. Nest's IoC container then reads TypeScript metadata emitted at compile time to resolve constructor parameters and inject dependencies automatically — no manual wiring required.

The @Controller, @Injectable, and @Module decorators are not the classic runtime decorator pattern; they are TypeScript decorators that attach metadata at class definition time. The framework reads this metadata at startup to build the route map and dependency graph. True runtime decoration in Nest appears in guards and interceptors, which wrap request handlers dynamically.

Takeaways

— Calling NestFactory.create(AppModule) returns a fully configured application instance without exposing HTTP server internals.

— The @Module decorator's imports array pulls in other modules' exported providers, enforcing explicit dependency boundaries between feature modules.

— Controllers handle only routing and parameter extraction; business logic lives in providers registered via the providers array.

— Nest's DI container reads TypeScript design:paramtypes metadata to resolve constructor arguments and inject the correct service instances.

— TypeScript decorators like @Controller and @Injectable attach metadata at class definition time, not at runtime — the framework reads this metadata during bootstrap to build the application graph.

— Runtime decorator behavior in Nest is implemented through interceptors and guards, which wrap route handlers to add logging, auth, or transformation logic.

Conclusions

The article's Mixue Ice Cream & Tea analogy is unusually effective because it maps directly to NestFactory.create() rather than stopping at a generic factory example — the consumer, the factory method, and the returned product all have exact framework counterparts.

Nest's choice to make the root module the single argument to create() means the entire application topology is declared in one module tree, which makes static analysis and code generation possible in ways that imperative wiring would not.

Calling TypeScript decorators 'the decorator pattern' is a common misconception; the article correctly distinguishes metadata decorators from runtime wrappers, but many Nest tutorials conflate the two, leading to confusion about when code actually executes.

Concepts & terms

IoC Container

Inversion of Control container — a registry that holds instantiated services and injects them into classes that declare a dependency, rather than requiring classes to instantiate their own dependencies with new.

design:paramtypes

TypeScript compiler-emitted metadata that records the types of constructor parameters. Nest reads this at runtime to determine which provider to inject into a controller or service constructor.

Provider

In Nest, any class annotated with @Injectable() and registered in a module's providers array. Providers contain business logic and can be injected into controllers or other providers via the DI container.

Source: juejin.cn ↗ Google Translate ↗ Backup ↗