NestJS

When to Use

• Structuring backend features into modules with clear boundaries
• Implementing cross-cutting concerns (auth, logging, validation, error handling)
• Designing provider patterns (DI scope, dynamic modules, factory providers)
• Building microservices or hybrid HTTP + message-based applications

When NOT to use:

• Simple scripts or CLI tools — NestJS module overhead is not worth it
• Serverless functions with cold-start constraints — consider lightweight alternatives
• Frontend code — this is backend-only architecture

Our Conventions