---
title: "#cqrs articles | Hashnode"
description: "Explore 79 articles tagged #cqrs on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/cqrs"
---

Tag

# #cqrs

79 posts · 14 followers

[Mattia Carcione](https://hashnode.com/@xeno-js) · [Oct 7](https://hashnode.com/posts/where-should-request-validation-live-in-a-typescript-application/6ac64239a72b603c8c0dbf15)

### [Where Should Request Validation Live in a TypeScript Application?](https://xeno-js.hashnode.dev/where-should-request-validation-live-in-a-typescript-application?utm_source=hashnode&utm_medium=feed)

Explore why validation belongs at the application boundary, how pipelines separate validation from HTTP, and how Xeno.JS implements this approach.

10 min read · [xeno-js.hashnode.dev](https://xeno-js.hashnode.dev/where-should-request-validation-live-in-a-typescript-application?utm_source=hashnode&utm_medium=feed)

[Dimitry Katz](https://hashnode.com/@basiliskin) · [Oct 6](https://hashnode.com/posts/why-cqrs-is-a-surprisingly-good-fit-for-orchestrating-coding-agents/6ac4e6d707bf43c812112b41)

### [Why CQRS Is a Surprisingly Good Fit for Orchestrating Coding Agents](https://basiliskin.hashnode.dev/why-cqrs-is-a-surprisingly-good-fit-for-orchestrating-coding-agents?utm_source=hashnode&utm_medium=feed)

Agents are long-running processes that need human input and recovery. Here’s how CQRS turn agent orchestration into a resilient, testable workflow.

13 min read · [basiliskin.hashnode.dev](https://basiliskin.hashnode.dev/why-cqrs-is-a-surprisingly-good-fit-for-orchestrating-coding-agents?utm_source=hashnode&utm_medium=feed)

[3](https://hashnode.com/posts/why-cqrs-is-a-surprisingly-good-fit-for-orchestrating-coding-agents/6ac4e6d707bf43c812112b41)

[Mattia Carcione](https://hashnode.com/@xeno-js) · [Oct 3](https://hashnode.com/posts/why-i-created-xeno-js-architectural-rigor-and-zero-infrastructure-constraints/6ac14714bac13faf39ff8227)

### [Why I Created Xeno.JS: Architectural Rigor and Zero Infrastructure Constraints](https://xeno-js.hashnode.dev/why-i-created-xeno-js-architectural-rigor-and-zero-infrastructure-constraints?utm_source=hashnode&utm_medium=feed)

Discover why Xeno.JS was created to solve technical debt and infrastructure lock-in in modern TypeScript applications.

4 min read · [xeno-js.hashnode.dev](https://xeno-js.hashnode.dev/why-i-created-xeno-js-architectural-rigor-and-zero-infrastructure-constraints?utm_source=hashnode&utm_medium=feed)

[Mattia Carcione](https://hashnode.com/@xeno-js) · [Oct 1](https://hashnode.com/posts/xeno-js-vs-nestjs-different-approaches-to-typescript-application-architecture/6abe8d6dcb5b3e74131062e7)

### [Xeno.JS vs NestJS: Different Approaches to TypeScript Application Architecture](https://xeno-js.hashnode.dev/xeno-js-vs-nestjs-different-approaches-to-typescript-application-architecture?utm_source=hashnode&utm_medium=feed)

Looking for a NestJS alternative? Compare Xeno.JS and NestJS for TypeScript application architecture, dependency injection, CQRS, pipelines, HTTP, and transport independence.

10 min read · [xeno-js.hashnode.dev](https://xeno-js.hashnode.dev/xeno-js-vs-nestjs-different-approaches-to-typescript-application-architecture?utm_source=hashnode&utm_medium=feed)

[N Chandra Prakash Reddy](https://hashnode.com/@ChandraPrakash1996) · [Sep 19](https://hashnode.com/posts/scaling-on-aws-refactoring-a-monolith-to-microservices/6aae6859d64231cad69c2457)

### [Scaling on AWS: Refactoring a Monolith to Microservices](https://devopstour.hashnode.dev/scaling-on-aws-refactoring-a-monolith-to-microservices?utm_source=hashnode&utm_medium=feed)

How to untangle legacy code, eliminate hidden state, and build AWS-native systems.

9 min read · [devopstour.hashnode.dev](https://devopstour.hashnode.dev/scaling-on-aws-refactoring-a-monolith-to-microservices?utm_source=hashnode&utm_medium=feed)

[Juan Miguel Nieto](https://hashnode.com/@jmnieto) · [Jul 31](https://hashnode.com/posts/appreciating-mediatr-by-jimmy-bogard/6a6c74ea09c7e5d1181e8d86)

### [Appreciating MediatR by Jimmy Bogard](https://jmnieto.hashnode.dev/appreciating-mediatr-by-jimmy-bogard?utm_source=hashnode&utm_medium=feed)

A write-up on understanding MediatR tradeoffs, syntaxes and exploring C# features that made it.

9 min read · [jmnieto.hashnode.dev](https://jmnieto.hashnode.dev/appreciating-mediatr-by-jimmy-bogard?utm_source=hashnode&utm_medium=feed)

[qodors](https://hashnode.com/@qodors) · [Jul 21](https://hashnode.com/posts/you-probably-don-t-need-mediatr/6a5f3fc3eb9af0ec714048fe)

### [You Probably Don't Need MediatR](https://qodors.hashnode.dev/you-probably-don-t-need-mediatr?utm_source=hashnode&utm_medium=feed)

The library gets added by habit. Here's the honest case for what it costs and when it's worth it.

5 min read · [qodors.hashnode.dev](https://qodors.hashnode.dev/you-probably-don-t-need-mediatr?utm_source=hashnode&utm_medium=feed)

[Hossein Esmati](https://hashnode.com/@desmati) · [Jun 26](https://hashnode.com/posts/cqrs-with-separate-read-write-models-in-net-core/6a3e64da15348f500bca8692)

### [CQRS with Separate Read/Write Models in .NET Core](https://nova-globen.hashnode.dev/cqrs-with-separate-read-write-models-in-net-core?utm_source=hashnode&utm_medium=feed)

This article is part of the Comprehensive Guide to Microservices Architecture in .NET Core, Cloud and Azure series. Understanding CQRS Command Query Responsibility Segregation (CQRS) is an architectur

5 min read · [nova-globen.hashnode.dev](https://nova-globen.hashnode.dev/cqrs-with-separate-read-write-models-in-net-core?utm_source=hashnode&utm_medium=feed)

[Coding Droplets](https://hashnode.com/@codingdroplets) · [May 30](https://hashnode.com/posts/domain-events-vs-integration-events-dotnet/6a1a4cf283cb9b0ebb1ee7b3)

### [Domain Events vs Integration Events in .NET: Which Should Your Team Use?](https://codingdroplets.hashnode.dev/domain-events-vs-integration-events-dotnet?utm_source=hashnode&utm_medium=feed)

Domain events vs integration events in .NET: key differences, when to use each, and how to decide for your ASP.NET Core team.

11 min read · [codingdroplets.hashnode.dev](https://codingdroplets.hashnode.dev/domain-events-vs-integration-events-dotnet?utm_source=hashnode&utm_medium=feed)

[Siddhesh Yellaram](https://hashnode.com/@siddheshy) · [Apr 6](https://hashnode.com/posts/stop-putting-everything-in-the-service-class-and-calling-it-clean-architecture/69d40e8740c9cabf447b9539)

### [Stop Putting Everything in the Service Class and Calling It Clean Architecture](https://siddheshy.hashnode.dev/stop-putting-everything-in-the-service-class-and-calling-it-clean-architecture?utm_source=hashnode&utm_medium=feed)

Clean Architecture isn’t about folder structures and CQRS isn’t about adding complexity they are about writing code your future self won’t have to rewrite.

10 min read · [siddheshy.hashnode.dev](https://siddheshy.hashnode.dev/stop-putting-everything-in-the-service-class-and-calling-it-clean-architecture?utm_source=hashnode&utm_medium=feed)
