SeoPatterns 1.0.1

NuGet Package: Business Layer Separation

This library allows you to separate your business layer from your controllers.

1. Create two concrete classes per endpoint in your controller:

• One implementing SeoPatterns.IBusinessRequest<TResponse>
• Another implementing SeoPatterns.IBusinessHandler<TRequest, TResponse>

2. Register dependencies using the following line:

• BusinessExecutionRegistration.Register(services, Assembly.GetExecutingAssembly());
• This will register IBusinessExecutioner and all your IBusinessHandler classes.

3. In your controller, inject IBusinessExecutioner and use it in your endpoint.

• Create an IBusinessRequest instance by passing all required inputs.
• Call IBusinessExecutioner.Process(IBusinessRequest).
• This will invoke the corresponding business layer (IBusinessHandler).

4. Use one BusinessHandler per endpoint.

• Consider adding a "Features" folder.
• Inside this folder, create a subfolder for each endpoint, containing its IBusinessRequest and IBusinessHandler.
• This makes it easier to manage your business logic.

Many developers create a single large business or service layer that handles logic for all endpoints, which can be difficult to maintain and violates the Single Responsibility Principle. This approach keeps your code modular and maintainable.

=============================================================================

In your Program.cs or StartUp.cs where you register all your dependencies

using SeoPatterns;

BusinessExecutionRegistration.Register(services, Assembly.GetExecutingAssembly());

or

BusinessExecutionRegistration.Register(builder.Services, Assembly.GetExecutingAssembly());

=============================================================================

using SeoPatterns;

public class TestController : ControllerBase
{
        private readonly IBusinessExecutioner _executioner;

        public TestController(IBusinessExecutioner executioner)
        {
            _executioner = executioner;
        }

        [HttpPost()]
        public async Task<ActionResult> Sample([FromBody] SampleInput input)
        {
            if (request == null) return BadRequest("Invalid data");

            var result = await _executioner.Process(new SampleBusinessRequest(input));

            return result.Success ? Ok() : StatusCode(result.StatusCode, result);
        }
}

=============================================================================

using SeoPatterns;

/// <summary>
/// The generic type 'TResponse' represents the return type of IBusinessHandler. You can use any object type you need (e.g., ServiceResult).
/// You can create as many properties as required.
/// The goal is to pass the input object from the controller endpoint through the constructor of this class and assign it to the internal properties.
/// These inputs will then be exposed to IBusinessHandler, where your business logic will be applied.
/// </summary>
public class SampleBusinessRequest : IBusinessRequest<ServiceResult>
{
    public SampleInput SampleInput { get; set; }

    public SampleBusinessRequest(SampleInput input)
    {
        SampleInput = input;
    }
}

=============================================================================

using SeoPatterns;

/// <summary>
/// The IBusinessHandler<TRequest, TResponse> interface represents the business layer.
/// The input objects from the controller are exposed through the 'request' object.
/// </summary>
public class SampleBusinessHandler : IBusinessHandler<SampleBusinessRequest, ServiceResult>
{
    public async Task<ServiceResult> Process(SampleBusinessRequest request, CancellationToken cancellationToken)
    {
        // Your business logic

        return ServiceResult.Ok();
    }
}