I am working an ASP.NET Core 6.0 Web API project. I use the CQRS design pattern.
I want to update an airlines table (code-first EF Core). So first I need to find the ID of airline.
I have GetAirlineByIdQueryHandler.cs
public record GetAirlineByIdQuery(int Id, bool LoadOverview = true) : IRequest<Airline>;
public class GetAirlineByIdQueryHandler : IRequestHandler<GetAirlineByIdQuery, Airline>
{
public async Task<Airline> Handle(GetAirlineByIdQuery request, CancellationToken cancellationToken)
{
var query = _techneDbContext.Airline
.Include(d => d.X)
.Include(d => d.Y)
.Include(d => d.Z)
.AsQueryable();
if (request.LoadOverview)
{
query = query.Include(d => d.Overview);
}
var airline = await query.FirstOrDefaultAsync(d => d.Id == request.Id);
if (airline == null)
{
throw new NotFoundException(nameof(Airline), request.Id);
}
return airline;
}
}
UpdateAirlineCommand.cs
public class UpdateAirlineCommand : AirlineUpdateDto, IRequest<Airline>
{
public int Id { get; set; }
}
public class UpdateAirlineCommanddHandler : IRequestHandler<UpdateAirlineCommand, Airline>
{
// removed constructor
public async Task<Airline> Handle(UpdateAirlineCommand request, CancellationToken cancellationToken)
{
// To update I have find the the id is there or not?
// Can I call GetAirlineByIdQueryHandler here or do I need to copy the query and paste it here
}
}
Generally Command and Queries operates on separate models. This gives you optimized data schemas for reads and writes. In your examples query returns the same model that will by updated by the command. Another drawback of using query inside command is making them tighly coupled. One of CQRS huge adventage is keeping read and write side separetly. In your example any change in GetAirlineByIdQueryHandler can affect UpdateAirlineCommanddHandler.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With