CQRS on ASP.net Core and the mediator pattern

From my experience, organizing a project, especially anything medium to large in size is always challenging. One of the ways that I found more success in doing so it’s implementing it using CQRS – Command Query Responsibility Segregation.

Due to the natural separation between the query and commands, organizing each and all the files related to a given command, like the value objects and validations give a clear idea of the functionality of the application and help multiple people to work on the project at the same time, as it’s easy to break in parts that can be worked in parallel.

I will be showing on this article how to configure an asp.net core project to use the mediator pattern to implement a simple CQRS on your project. Continue reading “CQRS on ASP.net Core and the mediator pattern” →

Helping your asp.net core web API behave!

We all have been around a couple of asp.net web API’s and it’s safe to safe that you can get productive pretty quickly with it, especially if you deploying it to an azure web app or already have an IIS to deploy to!

Sometimes also you inherit an API when you join a new project and the outlook doesn’t look too good. Endpoints that do not perform, different return status code for model validation and even more disparate information for exceptions and so on. 

The API is behaving badly! [slap on the hand!!!] I’ll share with you 3 approaches that helped me on the past to improve the API, giving you a quick way to identify slow endpoints, validating models and handling exceptions without need to change the controllers, relying on middlewares and on a global filter to achieve so.

You can find the full source code on this GitHub repo! 

behaving not being too slow!

This one is pretty handy if due it’s implementation on a middleware. If you try to put a timer/stopwatch inside your controller and you have one or more filters associated with the method, and your problem is on the filter itself, then you out on the cold.

Continue reading “Helping your ASP.NET Core API to behave” →