Found 21 packages
The set of marker interfaces used to define message types
R MessageBus Interfaces
Core serialization interfaces of SlimMessageBus
Core interceptor interfaces of SlimMessageBus
Core configuration interfaces of SlimMessageBus
ServiceConnect Interfaces
Core dependency resolver interfaces of SlimMessageBus
Contains the core message contracts for MicroBus which includes the command, query and event interfaces
PeachtreeBus Message Interfaces.
Base KnightBus Message Interfaces
Core interfaces and primitives for the HelixBus MessageBus system, including request/notification abstractions and pipeline behavior definitions.
Silverback is a powerful, elegant, and feature-rich message bus for .NET, designed to simplify asynchronous messaging, event-driven architectures, and microservice communication. With seamless integration for Apache Kafka and MQTT, it offers robust features for reliability, consistency, and scalability. This package contains the default messages interfaces and domain entity implementation.
Base Interfaces for FrameWork
Interface IItemProperty used in Microsoft.ServiceBus.Messaging.BrokeredMessage Properties to store properties about the actual class object in the body of the message
Merq: Message Bus (Commands + Events) mediator for internal application architecture via command and event messages. Only the main application assembly needs to reference this package. Components and extensions can simply reference the interfaces in Merq.Abstractions.
Abstractions and contracts for building event-driven applications with the Arcturus EventBus. Provides interfaces and base types for event publishing, subscription, and message handling.
Basic redis backed implementations of the interfaces in RegenerativeDistributedCache.Interfaces for an external (network) cache, a fan out pub/sub message bus, and a distributed locking mechanism for use with RegenerativeDistributedCache.RegenerativeCacheManager.
Merq: Default Message Bus (Commands + Events) Implementation, for internal application architecture via command and event messages. Only the main application assembly needs to reference this package. Components and extensions can simply reference the interfaces in Merq.
Some useful base classes and interfaces, mainly used with the Message Brokers. Apache Kafka, RabbitMQ or any other message broker integration will use or implement in generic fashion inside ASP.NET Core applications.
Message broker connector abstractions for WorkflowFramework — RabbitMQ, Azure Service Bus, and Kafka configuration models and interfaces.