This is the continuation of the previous article where I implemented the Pipes and Filters integration pattern but left out the continuous deployment aspect of it.

The way logging and instrumentation in code has traditionally been done is something like the below, say, I want to profile my application service method called “PeriodCloseReportAsync()” that gets called from my MVC controller action: This can be ok to a certain extent as long as the application is simple enough and you only intend […]

In a multi-tenant environment the application database is usually partitioned by tenants. This is done to achieve isolation and scalability. The problem of course is how do you route tenant requests to the correct databases?

It took trawling through dozens of blogs, MSDN help forums, git repo wikis and little bit of creative thinking to finally get the CI/CD pipeline working smoothly along with test reports showing in the build summary.

If you are not sure who this API is going to benefit and how, chances are You Ain’t Gonna Need It