Command Query Separation (CQS) for .NET and C#
- Build services that separate the responsibility of commands and queries
- Focus on implementing the handlers for commands and queries
- Create APIs with less boilerplate code
Available for:
🌐 ASP.NET Core
⚡ AWS Lambda
⚡ Azure Functions
⚡ Google Cloud Functions
🌐 ASP.NET Web API 2
Command Query Separation?
Queries: Return a result and do not change the observable state of the system (are free of side effects).
Commands: Change the state of a system but do not return a value.
In other words:
- Commands
- Writes (create, update, delete) data
- Queries
- Reads and returns data
The traditional approach that commands do not return a value is a bit inconvenient.
CommandQuery
has a pragmatic take and supports both commands with and without result 👍
Command Query Separation for .NET
- 📃 README: CommandQuery.md
- 💁 Samples:
Command Query Separation for ASP.NET Core
- 📃 README: CommandQuery.AspNetCore.md
- 💁 Samples:
Command Query Separation for AWS Lambda
- 📃 README: CommandQuery.AWSLambda.md
- 💁 Samples:
Command Query Separation for Azure Functions
- 📃 README: CommandQuery.AzureFunctions.md
- 💁 Samples:
Command Query Separation for Google Cloud Functions
- 📃 README: CommandQuery.GoogleCloudFunctions.md
- 💁 Samples:
Clients for CommandQuery APIs
- 📃 README: CommandQuery.Client.md
- 💁 Samples:
⬆️ Upgrading from version
3.0.0
to4.0.0
Upgrade AspNetCore:
- Upgrade the project target framework to
net8.0
Upgrade AWSLambda:
- Upgrade the project target framework to
net8.0
Upgrade AzureFunctions:
- Upgrade the project target framework to
net8.0
- Remove the
logger
argument fromHandleAsync
- Consider to use the
HttpRequest
versions ofHandleAsync
Upgrade GoogleCloudFunctions:
- Upgrade the project target framework to
net6.0
- Remove the
logger
argument fromHandleAsync
Inspired by Steven van Deursen blog posts: