The Repository pattern is one of those patterns that generates debate. Some say it’s essential, others call it unnecessary abstraction over EF Core. Here’s my pragmatic take on when and how to use it. What is the Repository Pattern? A repository abstracts data access, providing a collection-like interface to your domain objects. Instead of calling […]
Read more →Category: Software/System Design
CQRS Pattern Explained: Separating Reads from Writes
CQRS—Command Query Responsibility Segregation—sounds intimidating, but the core idea is simple. Separate your read operations from your write operations. Here’s why you’d want to do that and how to get started. The Problem In traditional CRUD applications, the same model handles both reads and writes. This works fine until: Your read queries need different data […]
Read more →Introduction to Event-Driven Architecture
I’ve spent the last year migrating systems from request-response to event-driven patterns. The shift in thinking is significant, but the benefits are real. Here’s my introduction to event-driven architecture (EDA) and why you should care. What is Event-Driven Architecture? Instead of services directly calling each other (request-response), they communicate through events. When something happens, a […]
Read more →Azure Cosmos DB – TTL (Time to Live) – Reference Usecase
TTL capability within Azure Cosmos DB is a live saver, as it would take necessary steps to purge redudent data based on the configurations you may. Let us think in terms of an Industrial IoT scenario, devices can produce vast amounts of telemetry information, logs and user session information that is only useful until we […]
Read more →Azure Cosmos DB–Multi Master
During the Ignite 2018, Microsoft has announced the general availability of Multi-Master feature being introduced to Azure Cosmos DB to provide more control into data redundancy and elastic scalability for your data from different regions with multiple writes and read instances. What is Multi-Master essentially? Multi-master is a capability that provided as part of Cosmos […]
Read more →Azure Cosmos DB – 429 Too Many Requests
Recently while I was doing Performance Testing in one of the APIs interacting with Cosmos DB, I encountered a problem as Azure Cosmos DB API’s started returning Http Code 429. Http Status Code 429 indicates that too many request been received or request rate is very large. This error would happen when we have concurrent […]
Read more →