Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Command Query Separation for 🌐ASP.NET Core ⚡AWS Lambda ⚡Azure Functions ⚡Google Cloud Functions

License

NotificationsYou must be signed in to change notification settings

hlaueriksson/CommandQuery

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

buildCodeFactor

CommandQueryCommandQuery.Abstractions

CommandQuery.AspNetCoreCommandQuery.AWSLambdaCommandQuery.AzureFunctionsCommandQuery.GoogleCloudFunctions

CommandQuery.Client

Content

Introduction

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

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.

Martin Fowler

In other words:

  • Commands
    • Writes (create, update, delete) data
  • Queries
    • Reads and returns data

The traditional approach that commandsdo not return a value is a bit inconvenient.

CommandQuery has a pragmatic take and supports both commands with and without result 👍

Packages

CommandQuery ⚙️

NuGetNuGet

Command Query Separation for .NET

CommandQuery.AspNetCore 🌐

NuGetNuGet

Command Query Separation for ASP.NET Core

CommandQuery.AWSLambda

NuGetNuGet

Command Query Separation for AWS Lambda

CommandQuery.AzureFunctions

NuGetNuGet

Command Query Separation for Azure Functions

CommandQuery.GoogleCloudFunctions

NuGetNuGet

Command Query Separation for Google Cloud Functions

CommandQuery.Client 🧰

NuGetNuGet

Clients for CommandQuery APIs

Upgrading

⬆️ Upgrading from version3.0.0 to4.0.0

Upgrade AspNetCore:

  • Upgrade the project target framework tonet8.0

Upgrade AWSLambda:

  • Upgrade the project target framework tonet8.0

Upgrade AzureFunctions:

  • Upgrade the project target framework tonet8.0
  • Remove thelogger argument fromHandleAsync
  • Consider to use theHttpRequest versions ofHandleAsync

Upgrade GoogleCloudFunctions:

  • Upgrade the project target framework tonet8.0
  • Remove thelogger argument fromHandleAsync

Acknowledgements

Inspired bySteven van Deursen blog posts:

About

Command Query Separation for 🌐ASP.NET Core ⚡AWS Lambda ⚡Azure Functions ⚡Google Cloud Functions

Topics

Resources

License

Stars

Watchers

Forks


[8]ページ先頭

©2009-2025 Movatter.jp