Create Command then Read Query

Hi,

Is it okay to call a create command and then the read to get the newly created record? (I have some loosely coupled objects which require some additional mapping to get the related entities)

public async Task<IActionResult> Post([FromBody] Create.Command command)
{
    if (!ModelState.IsValid) return BadRequest(ModelState);
    var result = await _mediator.Send(command);
    return Ok(_mediator.Send(new GetById.Query {Id = result.Id}));
}

[GabrielHSFerreira]

I guess it have no problem since both calls are being made on your application entry point. What you should avoid is call Mediator.Send inside a Handler that responds to a previous Mediator.Send.

[OculiViridi]

@TDK1964 “RESTful-ly” speaking, a Controller method that creates an entity should return the created entity’s Id. And also, the corresponding HTTP status response should be 201 Created. Why not changing the implementation of your Create.Command, to persist the entity and then return the corresponding Id, so you can avoid the “ugly” 2 calls to Mediator?