create-service

A structured backend service layer in TypeScript places business logic in services, uses dependency injection for coupling, and defines return-type contracts with domain-centric errors. Components reside under src/services with the {name}.service.ts naming convention.

Use a resource service for CRUD operations on domain entities and a utility service for cross-cutting concerns like authentication or notifications. Distinguishing between them ensures proper separation of concerns in your service-oriented architecture.

The best way to organize service files is placing them under src/services and following the {service-name}.service.ts naming convention. This aligns with existing repositories and maintains consistency across the TypeScript project structure.

Handling domain errors in a service layer requires throwing domain-centric errors and enforcing return-type contracts that return domain types. This keeps business logic decoupled from transport-layer concerns and preserves type safety.

Yes, this guide applies to TypeScript projects using a repository layer and service-oriented architecture. It aligns new services with existing repositories to maintain consistent data access patterns and dependency injection.

Business logic should live in services to keep controllers thin and ensure domain rules are centralized, testable, and reusable. Services manage dependencies and return domain types, preventing logic leakage into the transport layer.