Structured Node applications.
WHAT IT IS
A framework providing structure and conventions on top of Node.
WHAT IT PROVIDES
Modules, controllers and services Dependency injection Validation through decorators Built-in support for several transport layers Testing utilities
WHY IT EXISTS
Because unstructured Node applications diverge, and large teams need consistency.
WHAT IT RESEMBLES
Frameworks from other ecosystems with strong conventions.
WHAT DEPENDENCY INJECTION PROVIDES
Services supplied rather than constructed, which makes them replaceable and testable.
WHAT THE STRUCTURE IS
Controllers handling requests Services containing logic Modules grouping related pieces
WHAT IT COSTS
A learning curve More ceremony than a small application needs
WHAT IT SUITS
Larger applications Teams needing consistency Long-lived systems
WHAT IT DOES NOT SUIT
Small services, where the structure exceeds the problem.
WHAT TO USE IT WITH
TypeScript, which it assumes.
WHAT TO ESTABLISH
Whether the scale justifies the structure.
