service-patterns

What problem does it solve?

Services contain all business logic. They are the heart of the application, orchestrating operations between controllers and data access.

Core Features & Use Cases

• Interface-Based Design: Always define an interface for each service
• ServiceResult Pattern: Use a result wrapper that indicates success/failure and error type
• Business Logic Encapsulation: Place all business rules in services, not controllers
• Structured Logging: Employ semantic logging with named parameters and appropriate levels
• Error Handling: Let unexpected exceptions bubble to a global handler
• Mapping & Registration: Map domain models to responses and register services in DI

Quick Start

Register the service in your DI container and begin using the service methods in your controllers