Distributed lock using PostgreSQL
This post talks about why you may need a distributed lock and how you can create a distributed lock using PostgreSQL.
Category: Architecture
Passing correlation id across requests
This post describes importance of passing a single correlation id across requests in microservices and how we an achieve this in .NET.
Integrity of Collections in Domain-Driven Design
The post describes the issues with Collection integrity in DDD and how we can use ImmutableList to avoid manipulating collections outside the Domain.
Client library for your Rest API – Is it worth the pain?
Creating a client library for your Rest service can help your clients consume your Rest API. But is it a silver bullet to every problem?
Running an ASP.NET Core application against multiple DB providers – Part 1
In my previous post, I had talked about how we to ported an existing repository code from Azure SQL to Amazon Aurora. This is a two-series post where I will throw a little bit more light on the intention behind it and what we were trying to achieve. Background We had a small ASP.NET Core solution
Azure SQL to Cosmos DB – Lesson Learnt
We are currently working on a greenfield project which involves building several microservices on Azure. One of our primary services had Azure SQL as its data source originally. But, midway during the development, we decided to switch Cosmos DB instead. One of the main motivations for this switch was that it was too hard to
Sending message from Azure Functions to NServiceBus receiver
NServiceBus is one of the most widely used service bus in .NET World. It offers features like high performance, scalability, automatic retries, auditing and so-on. NService has an out-of-box support for MSMQ, RabbitMQ, Sql Server, Azure Service Bus, etc. Our organization uses NServiceBus for messaging and workflow. We use Azure Service Bus in test/production and