Why I have overused the CQRS pattern

In this post, I want to share how I might have overused the Command Query Responsibility Segregation (CQRS) pattern when developing .NET applications that follow clean architecture.

Notes on the Interface Segregation Pattern

The Interface Segregation Pattern (ISP) is one of the principle in SOLID. As a recap, SOLID is an acronym which stands for the five software design principles:

• The Single Responsibility Principle
• The Open Closed Principle
• The Liskov Substitution Principle
• The Interface Segregation Principle
• The Dependency Inversion Principle

The Open Closed Principle

In this post, I continue to share what I have learned about the SOLID principles in the book “Clean Architecture A Craftsman’s Guide to Software Structure and Design”. As a recap, six principles make up the SOLID acronym:

• The Single Responsibility Principle.
• The Open Closed Principle.
• The Liskov Substitution Principle.
• The Interface Segregation Principle.
• The Dependency Inversion Principle.

In the previous post, I wrote about the Single Responsibility Principle. In this post, I write about the Open Closed Principle.

The Single Responsibility Principle

Recently, I read the book “Clean Architecture” by Robert C. Martin. Overall, this is a great book with a wealth of information on software design principles to guide developers to build scalable, maintainable and flexible applications. A core part of the book discusses about six design principles which together make up the acronym SOLID.