Messaging

📘 Resources

• DDD and Messaging Architectures
• clemensv/messaging - Resource collection for messaging and eventing
• Messaging Playlist - CodeOpinion
• Martin Kleppmann Yotube

📕 Articles

• Communication in a microservice architecture
• Asynchronous message-based communication
• Modular Monolith: Integration Styles
• Marrying RESTful HTTP with Asynchronous and Event-Driven Services
• DDD and Messaging Architectures
• Asynchronous Messaging Patterns
• Message Properties
• Message Naming Guidelines
• Organizing (Commands, Events & Handlers) in Microservices
• REST APIs for Microservices? Beware!
• Messaging Commands & Events Explained!
• Event Choreography & Orchestration (Sagas)
• Outbox Pattern: Reliably Save State & Publish Events
• Handling Duplicate Messages (Idempotent Consumers)
• Message-IDs for Handling Concurrency
• CAP: Event Bus & Outbox Pattern
• Message Queue Overload from High Processing Latency
• Processing commands with Hangfire and MediatR
• Using Hangfire and MediatR as a Message Dispatcher
• Idempotent Aggregates
• Identify Commands & Events
• Idempotent Commands
• Moving work Out-of-Process using Brighter and RabbitMQ
• Thin vs Fat Integration Events
• Events: Fat or Thin
• Events on the Outside vs Events on the Inside
• Patterns for Decoupling in Distributed Systems: Fat Event
• Message Sender: Who Sent the Command/Event?
• Why use DTOs (Data Transfer Objects)?
• Event Versioning Guidelines
• Fat vs thin domain events
• Putting your events on a diet
• What do you mean by “Event-Driven”?
• Are CQRS commands part of the domain model?
• DTO vs Value Object vs POCO
• Event Based Architecture: What do you mean by EVENT?
• What’s the difference between a command and an event?
• Outbox, Inbox patterns and delivery guarantees explained
• Distributed State — Challenges and Options
• Message Naming Conventions
• Building an Event Driven .NET Application: The Fundamentals
• Building an Event Driven .NET Application: Setting Up MassTransit and RabbitMQ
• Kafka vs RabbitMQ vs AWS SNS/SQS: Which Broker to Choose?
• Event Pitfalls (and How to Avoid Them)
• Designing Domain Events
• Competing Consumers Pattern for Scalability
• Patterns for Decoupling in Distributed Systems: Explicit Public Events
• Event immutability and dealing with change
• Transient fault handling
• SHARING DATA BETWEEN MODULES IN MODULAR MONOLITH
• Comparing Techniques for Communicating Between Services
• Bus or Queue
• Improving Monolith’s Availability
• The Outbox Pattern in Event-Driven ASP.NET Core Microservice Architectures
• Competing Consumers
• Competing Consumers pattern
• REST vs Messaging for Microservices – Which One is Best?
• RPC vs. Messaging – which is faster?
• Microservices patterns: synchronous vs asynchronous communication
• Async request processing
• Event Feeds: Simple and reliable messaging infrastructure
• What’s the difference between a command and an event?
• Events should be as small as possible, right?
• How to build a simple event pipeline
• Wire Tap Enterprise Integration Pattern
• Wire Tap
• Message Ordering in Pub/Sub or Queues
• Mapping event type by convention
• Distributed systems evolution: message contracts
• Back to Basics: commands, events, and messages
• Define messages as POCO, interfaces, or records. Does it really matter?
• Internal and external events, or how to design event-driven API
• How Discord Stores Trillions of Messages

📺 Videos

• Handling Concurrency with Message-IDs | Event Driven Architecture
• Message Naming Guidelines | Event Driven Architecture
• Event Versioning Guidelines
• Organizing (Commands, Events & Handlers) in Microservices/SOA
• Service Oriented Architecture: Commands & Events Explained!
• Handling Duplicate Messages (Idempotent Consumers)
• Sagas: Event Choreography & Orchestration (NServiceBus)
• CAP: Event Bus & Outbox Pattern
• Thin or Fat Events? Are your boundaries right?
• GOTO 2017 • The Many Meanings of Event-Driven Architecture • Martin Fowler
• On .NET Live - Messaging Patterns for .NET Developers
• Competing Consumers Pattern for Scalability | Message Queues
• Event Driven Architecture for Real-Time Web
• Learnings from Running 1000s of Production RabbitMQ Clusters • Lovisa Johansson • RabbitMQ Summit
• What is Event Driven Architecture? (EDA - part 1)
• The Saga Pattern in Microservices (EDA - part 2)
• GOTO 2019 • Temporal Modelling • Mathias Verraes
• Handling Failures in Message Driven Architecture
• Building a Mediator library in .NET from scratch
• Message Driven Architecture to DECOUPLE a Monolith
• Synchronous vs Messaging: When to use which?
• Moving work Out-of-Process using Brighter and RabbitMQ
• Building a Request Pipeline for Separating Concerns with Pipes & Filters
• Distributed Messaging Patterns
• RPC vs Messaging: When to use which?
• Beyond REST and RPC: Asynchronous Eventing and Messaging Patterns
• Modern .NET Messaging using MassTransit
• Was that message processed? Asynchronous Request-Response Pattern
• Messaging Building Blocks: Commands & Events
• Message delivery (at least-once, at most-once, exactly once?) | Messaging in distributed systems
• Message Ordering in Pub/Sub or Queue
• Avoiding a QUEUE Backlog Disaster with Backpressure & Flow Control
• Avoiding Batch Jobs by a message in the FUTURE
• Wolverine: Your Next Messaging Library
• Clean Message Bus Consumers with MediatR in .NET
• Using Open Telemetry with the MassTransit Test Harness?
• MassTransit Message Contract Sharing using NuGet
• Versioning your MassTransit message contracts

📦 Libraries

• Enexure.MicroBus - MicroBus is a simple in process Mediator for .NET
• Foundatio - A common interface with in memory, redis and azure implementations.
• Kledex - .NET Standard framework to create simple and clean design. Advanced features for DDD, CQRS and Event Sourcing.
• MQTTnet - Tnet is a high performance .NET library for MQTT based communication.
• OpenCQRS - .NET Core library for DDD, CQRS and Event Sourcing with Azure Service Bus integration. Supported database providers for the Command and the Event stores are: DocumentDB, MongoDB, SQL Server, MySQL, PostgreSQL and SQLite.
• Rebus - Simple and lean service bus implementation for .NET.
• RestBus - Messaging library for RabbitMq.
• tossit - Simple, easy to use library for distributed job/worker logic. Distributed messages handled by built in RabbitMQ implementation.
• Steeltoe - Steeltoe .NET Core Components: CircuitBreaker, Configuration, Connectors, Discovery, Logging, Management, and Security
• MetroBus - Lightweight messaging wrapper of
• Abp - Open Source Web Application Framework for ASP.NET Core
• OpenSleigh - OpenSleigh is a Saga management library for .NET Core.
• knightbus - Fast multi-transport messaging framework
• SlimMessageBus - Lightweight message bus interface for .NET (pub/sub and request-response) with transport plugins for popular message brokers.
• silverback - Silverback is a simple but feature-rich framework to build reactive/event-driven applications or microservices with .net core.
• Obvs - An observable microservice bus library for .NET, that wraps the underlying message transports in simple Rx based interfaces.
• Platibus - Decentralized asynchronous messaging framework
• EventBus - A .NET Core ultra lightweight in-memory event bus implementation.
• Enbiso.NLib - .Net Standard Libraries for Microservices
• eventbus - A simple Event Bus abstraction layer for working with events in .NET.
• AzureFromTheTrenches.Commanding - A configuration based commanding and mediator framework that supports command dispatch and execution in-process, over HTTP or over Azure Storage Queues. Written to .NET Standard 2.0 and supports many popular runtimes including .NET Core and .NET 4.6.x.
• Brighter - Command Dispatcher, Processor, and Distributed Task Queue
• Darker - The query-side counterpart of Brighter
• MassTransit - Distributed Application Framework for .NET
• ViennaNET - Framework for quickly creating enterprise microservices on .NET Core
• MemBus - Pure In-Memory Publish/Subscribe .NET Bus
• Cysharp/MagicOnion - Unified Realtime/API framework for .NET platform and Unity.
• eventflow/EventFlow - Async/await first CQRS+ES and DDD framework for .NET
• dasiths/SimpleMediator - A .NET/C# implementation of the mediator pattern with support for queries, commands and events
• mayuanyang/Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
• FoundatioFx/Foundatio - Pluggable foundation blocks for building distributed apps.
• AsynkronIT/protoactor-dotnet - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin
• Abc-Arbitrage/Zebus - A lightweight Peer to Peer Service Bus
• Shriek-Projects/shriek-fx - An easy-to-use rapid development framework developed on the basis of.NET Core 2.0, following the constraints of domain Driven Design (DDD) specifications, combined with the CQRS architecture to provide the infrastructure for event-driven, event backtracking, responsiveness, and more.
• daxnet/apworks-core - Apworks framework supporting .NET Core
• nats-io/nats.net - The official C# Client for NATS
• zeromq/netmq - A 100% native C# implementation of ZeroMQ for .NET
• zeromq/clrzmq4 - ZeroMQ C# namespace (.NET and mono, Windows, Linux and MacOSX, x86 and amd64)
• ThreeDotsLabs/watermill - Building event-driven applications the easy way in Go.
• Cysharp/MessagePipe - High performance in-memory/distributed messaging pipeline for .NET and Unity.
• cfrenzel/Eventfully - Lightweight Reliable Messaging Framework using Outbox Pattern / EFCore / AzureServiceBus
• daniellittledev/Enexure.MicroBus - MicroBus is a simple in process Mediator for .NET
• simplesoft-pt/Mediator - Small .NET library that helps with the implementation of mediator pattern for commands, events and queries
• gautema/CQRSlite - A lightweight framework to help creating CQRS and Eventsourcing applications in C#
• martinothamar/Mediator - A high performance implementation of Mediator pattern in .NET using source generators.
• AlphaYu/Adnc - The microservice framework is also suitable for the development of monolithic architecture systems. It supports the classic three-tier and DDD architecture development model, and integrates a series of mainstream and stable microservice supporting technology stacks. A framework with front-end and back-end separation. The front-end is based on Vue and the back-end is built on .Net 5.0.
• Im5tu/OpenMessage - Receive messages from multiple sources using a centralised delivery pipeline
• SorenZ/Alamut.Kafka - An opinionated approach to use Apache Kafka in Dotnet
• revoframework/Revo - Event Sourcing, CQRS and DDD framework for C#/.NET Core.
• MesutAtasoy/Joker.Packages
• oskardudycz/EventSourcing.NetCore/event-pipelines
• GDATASoftwareAG/motornet - Motor.NET is a microservice framework based on Microsoft.Extensions.Hosting
• litenova/LiteBus - An easy-to-use and ambitious in-process mediator to implement CQS with minimum reflection usage and streamable query support.
• NHadi/Dermayon - Dermayon is Library for supporting build large application,distributed application, scalable, microservices, cqrs, event sourcing, including generic ef repository pattern with unit of work, generic mongo repository pattern with unit of work, kafka, etc
• cloudnative-netcore/netcorekit - A crafted toolkit for building cloud-native apps on the .NET platform
• lucabriguglia/OpenCQRS - .NET Standard framework to create simple and clean design. Advanced features for DDD, CQRS and Event Sourcing.
• Eventuous/eventuous - Minimalistic Event Sourcing library for .NET
• christophe-mommer/CQELight
• Bullabs/Qitar - Domain Driven Design oriented application framework.
• yang-xiaodong/Savorboard.CAP.InMemoryMessageQueue - In-Memory message queue for CAP
• osstotalsoft/nbb
• liuhll/silky - The Silky framework is designed to help developers quickly build a microservice development framework through simple code and configuration under the .net platform.
• JasperFx/wolverine - Next Generation .NET Command and Message Bus
• boyney123/eventcatalog - Discover, Explore and Document your Event Driven Architectures powered by Markdown.
• EasyDesk/easydesk-clean-architecture - A microservice framework based on the Clean Architecture and the Domain Driven Design.
• dotnet/aspire - .NET Aspire is an opinionated, cloud ready stack for building observable, production ready, distributed applications

📚 Books

• Enterprise Integration Patterns
• Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems
• Making Sense of Stream Processing
• Streaming Systems: The What, Where, When, and How of Large-Scale Data Processing
• Designing Event-Driven Systems
• Building Event-Driven Microservices: Leveraging Organizational Data at Scale
• Practical Event-Driven Microservices Architecture: Building Sustainable and Highly Scalable Event-Driven Microservices