Topics and subscriptions vs queues
Each queue sends each message it contains to a single consumer. So, if you have multiple consumers interested in the same message, only one of… Read More »Topics and subscriptions vs queues
Refresher on inbox and outbox patterns
The Outbox Pattern Purpose: avoid the need for distributed transactions when a single workflow involves both in-process and out-of-process transactions. For example, a request to… Read More »Refresher on inbox and outbox patterns
Manually cancelling async delays in .NET
Task.Delay(TimeSpan duration, CancellationToken cancellationToken) allows you to asynchronously wait for a certain duration before continuing. Sometimes, however, we want to manually cancel the delay before… Read More »Manually cancelling async delays in .NET
Best practices for exceptions
Consider the following: In some cases the exception thrown is completely expected, such as an OperationCancelledException. In this case, it’s not really an error, and… Read More »Best practices for exceptions
Implementing The Outbox Pattern with Laravel
Source code available on GitHub at https://github.com/jlwalkerlg/laravel-outbox-pattern-demo. Laravel’s event system makes it simple to implement the outbox pattern and deal with failures in processing side… Read More »Implementing The Outbox Pattern with Laravel
The Outbox Pattern
The Problem When publishing messages to a message broker, it’s important to recognise that this publishing falls outside the scope of any database transaction you… Read More »The Outbox Pattern
Is Morality Objective?
When speaking of the possibility of an objective morality, most people want to be able to say that certain practices are right or wrong regardless… Read More »Is Morality Objective?
The Application Layer
Take a look at the standard diagram of The Clean Architecture, and you’ll notice a layer labelled “Application Business Rules”, wherein the “Use Cases” are… Read More »The Application Layer
The Clean Architecture
The Clean Architecture is one of many architectures that aim to isolate the domain model, and make the code base more modular, more decoupled, and… Read More »The Clean Architecture
Command Query Responsibility Segregation
CQRS is an architectural pattern whereby the system is separated according to two distinct responsibilities: reads/queries, and writes/commands. The basis for doing so is to… Read More »Command Query Responsibility Segregation
Package By Feature
File organisation plays an important role in the discoverability of code and the overall cohesiveness of your application. It determines how easily developers can find… Read More »Package By Feature
Encapsulation
Encapsulation is one of the four pillars of object-oriented programming, along with abstraction, inheritance and polymorphism. The idea is to restrict access to an object’s… Read More »Encapsulation