Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by using MediatR
Enhancing Request Pipelines with MediatR Behaviors
Introduction MediatR is a widely used library in .NET applications that follows the mediator pattern, helping to decouple requests from handlers. While it simplifies CQRS (Command Query Responsibility Segregation), it also offers a robust feature called Pipeline Behaviors. These behaviors enable developers to intercept requests and implement cross-cutting concerns such as logging, validation , performance tracking , transaction management , and error handling in a structured and reusable manner.
MediatR is a library that implements the Mediator pattern, facilitating communication between different parts of an application without them being directly coupled. This promotes a more modular and flexible design. It is widely used in applications to manage commands and events in a centralized way. In this example, we will see how to use MediatR to send a command and process its response in a handler.
O MediatR é uma biblioteca que implementa o padrão Mediator, facilitando a comunicação entre diferentes partes de uma aplicação sem que elas precisem estar diretamente acopladas. Isso promove um design mais modular e flexível. Ele é amplamente utilizado em aplicações para gerenciar comandos e eventos de forma centralizada. Neste exemplo, veremos como utilizar o MediatR para enviar um comando e processar sua resposta em um manipulador.
What is Clean Architecture: Part 19 -Add Controllers
In this article, we’ll see how to build lightweight and loosely coupled API controllers using MediatR in an ASP.NET Core 8 application. We’ve already set up the essential layers—Application, Infrastructure, and Persistence—and now it’s time to expose functionality through an API that communicates with the core of our application using the MediatR pattern. Why Use MediatR?
What is Clean Architecture: Part 13-Adding Validation Using Fluent Validation
In modern application development, ensuring that data is valid before processing is crucial to maintain application integrity. Whether you're creating, updating, or deleting entities, it is important to verify that the data adheres to business rules. In this article, we will focus on how to add validation using Fluent Validation in a feature-based architecture, specifically within a command handler for creating events.
Implementing CQRS with MediatR in .NET 8: A Complete Guide
The CQRS (Command Query Responsibility Segregation) pattern is an architecture that separates the operations of reading (Query) and writing (Command) within a system. This separation allows for each operation to be scaled and optimised independently. In the .NET ecosystem, one of the most popular packages for implementing CQRS is MediatR, which facilitates the mediation of commands and queries. What is CQRS?
Understanding the Mediator Pattern in .NET
In complex applications, components often need to communicate with each other. Traditionally, this can be achieved by having components directly interact with one another. However, this approach can lead to a tightly coupled system where changes in one component might necessitate changes in others, leading to a maintenance nightmare. This is where the Mediator pattern comes into play.
πHow to Use MediatR Pipeline Behavior in .NET 8
In modern software development, ensuring that our applications are maintainable, testable, and scalable is crucial. One tool that has gained popularity for achieving these goals in .NET applications is MediatR. MediatR facilitates the implementation of the mediator pattern, which helps in reducing the direct dependencies between components. One of its powerful features is Pipeline Behavior, which allows you to add pre- and post-processing steps to your request handling.
Domain Events
Introduction to domain events Definition of domain events: Domain events are events that occur in a specific area or domain and are important for the business logic of an application. They represent significant state changes or activities within the system. In contrast to system-wide events, which can affect the entire application, domain events are closely linked to the specific domain or specialist area of your application.
Mastering CQRS Design Pattern with MediatR in C# .NET
INTRODUCTION The Command Query Responsibility Segregation (CQRS) pattern separates the concerns of read and write operations in an application by using separate models for handling commands (writing data) and queries (reading data). When implementing CQRS in C#, MediatR is a popular library that facilitates the implementation of the pattern by acting as a mediator between commands, queries, and their respective handlers. Key Components: Commands: Represent actions that mutate application state.
ASP.NET 8 - Authentication and Authorization in 7 steps.
In this tutorial, you will learn how to develop an API for user permission-based authentication and authorization. In addition, the Clean Architecture, Unit of Work, and Mediator patterns will be used. C# .NET8 Visual Studio 2022 Docker Azure Data Studio This pattern aims to improve the way different parts of your application communicate with each other. Different parts of your application (components) don't talk directly to each other.
MediatR Response: Should the Request Handler Return Exceptions?
Original article on Medium In the evolving landscape of software architecture, the choice between traditional exception handling and adhering to functional programming principles to manage errors directly impacts system design and reliability. Clean architecture advocates for systems independent of frameworks, UI, databases, and external agencies. This independence is crucial for maintaining the system's integrity over time.
造轮子之EventBus - 饭勺oO - 博客园
前面基础管理的功能基本开发完了，接下来我们来优化一下开发功能，来添加EventBus功能。 EventBus也是我们使用场景非常广的东西。这里我会实现一个本地的EventBus以及分布式的EventBus。 分别使用MediatR和Cap来实现。 现在简单介绍一下这两者： MediatR是一个轻量级的中介者库，用于实现应用程序内部的消息传递和处理。它提供了一种简单而强大的方式来解耦应用程序的不同部分，并促进了代码的可维护性和可测试性。使用MediatR，您可以定义请求和处理程序，然后通过发送请求来触发相应的处理程序。这种模式使得应用程序的不同组件可以通过消息进行通信，而不需要直接引用彼此的代码。MediatR还提供了管道处理功能，可以在请求到达处理程序之前或之后执行一些逻辑，例如验证、日志记录或缓存。...
使用MediatR和FluentValidation实现CQRS应用程序的数据验证 - 赵榕 - 博客园
本文将重点介绍如何通过MediatR的管道功能将FluentValidation集成到项目中实现验证功能。 什么是CQRS？ CQRS（Command Query Responsibility Segregation）也叫命令查询职责分离，是近年来非常流行的应用程序架构模式。CQRS 背后的理念是在逻辑上将应用程序的流程分成两个独立的流程，即命令或查询。 命令用于改变应用程序的状态。对应CRUD的创建、更新和删除部分。查询用于检索应用程序中的信息，对应CRUD的读取部分。 优点： 单一职责 – 命令和查询只有一个职责。要么更改应用程序的状态，要么检索它。因此它们很容易推理和理解。 解耦 – 命令或查询与其处理程序完全解耦，因此在处理程序方面有很大的灵活性，可以按照自己认为最合适的方式来实现。 可扩展性 – CQRS 模式在如何组织数据存储方面非常灵活，为您提供了多种可扩展性选择。您可以将一个数据库用于命令和 查询。您可以使用独立的读/写数据库来提高性能，并在数据库之间使用消息传递或复制来实现同步。 可测试性 –...
OnionArch 2.0 - 基于DDD的洋葱架构改进版开源
大家好，去年我发布了一篇 OnionArch - 采用DDD+CQRS+.Net 7.0实现的洋葱架构 。很多程序员都比较感兴趣，给我要源代码。这次我把OnionArch进行了升级，改进了一些特性，并放出源代码，iamxiaozhuang/OnionArch2 (github.com) 欢迎大家研究使用。 一、自动生成和发布领域事件 我在OninArch1.0实现了对删除的实体自动生成和发布领域事件，并通过订阅这个领域事件，将删除的实体数据备份至回收站表中，以备审计和数据恢复。 本次我改进了这个特性，对实体数据的新增，修改和删除都会自动生成和发布领域事件。我认为尽量不要通过修改代码来新增和发布领域事件，这会导致新增的业务功能也需要修改代码而不是新增代码来实现，不符合对修改关闭和对扩展开放的设计原则。应该对实体数据的任何变动都自动发布领域事件，然后在事件Handler中筛选需要的领域事件并进行处理。 我基于这个特性实现了按配置自动审计记录和和按配置自动发布集成事件功能。 按配置自动审计功能 我们可以通过配置的方式来实现那些实体，那种修改类型，那个字段需要审计。请看如下配置：...
Applying the CQRS Pattern in an ASP.NET Core Application
CQRS is a well-known architectural pattern that can solve many problems encountered in complex scenarios. Check out in this blog post how this pattern works and how to implement it in an ASP.NET Core application. There are some situations where it is necessary to separate reading and writing functions, mainly in complex scenarios or that demand great scalability of resources.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with using
Contact using, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack