Namespace Silverback.Messaging.Messages

Classes

BinaryMessage

A binary message that is being transferred over the message broker without serializing and deserializing it.

DefaultMessageHeaders

Contains the constants with the names of the standard message headers used by Silverback.

HeaderAttribute

Used to decorate a property which value must be produced/consumed as message header.

InboundEnvelopeBuilderExtensions

Adds the WithOffset methods to the InboundEnvelopeBuilder<TMessage>.

InboundEnvelopeBuilder<TMessage>

Creates the IInboundEnvelope<TMessage> instances to be used for testing.

KafkaEnvelopeExtensions

Adds some convenience extension methods to the envelope interfaces.

KafkaKeyMemberAttribute

The values of the properties decorated with this attribute are used to build the message key that will be used by Kafka (for partitioning, compacting, etc.).

KafkaMessageHeaders

Contains the constants with the names of the Kafka specific message headers used by Silverback.

MessageHeader

A header added to the message being sent over a message broker.

MessageHeaderCollection

A modifiable collection of message headers.

MessageHeaderEnumerableExtensions

Add some helper methods to the IEnumerable<T> of MessageHeader.

MessagesSource<TBaseEvent>

The default generic implementation of IMessagesSource. It contains some protected methods to add the internal events to a temporary collection exposed via the IMessagesSource implementation.

MqttEnvelopeExtensions

Adds some convenience extension methods to the envelope interfaces.

MqttMessageHeaders

Contains the constants with the names of the Kafka specific message headers used by Silverback.

OutboundEnvelopeBuilder<TMessage>

Creates the IOutboundEnvelope<TMessage> instances to be used for testing.

Tombstone

A tombstone message (a message with null body).

Tombstone<TMessage>

A tombstone message (a message with null body).

The event published when an exception occurs during the processing of a (database) transaction. It is fired by the data access while saving changes (see Silverback.Core.EntityFrameworkCore) and it is internally used (in Silverback.Integration) to trigger additional tasks related to the publishing of the domain events.

TransactionCompletedEvent

The event published when a (database) transaction is completed and committed. It is fired by the data access after saving changes (see Silverback.Core.EntityFrameworkCore) and it is internally used (in Silverback.Integration) to trigger additional tasks related to the publishing of the domain events.

TransactionStartedEvent

The event published when a (database) transaction is being started. It is fired by the data access before saving changes (see Silverback.Core.EntityFrameworkCore) and it is internally used (in Silverback.Integration) to trigger additional tasks related to the publishing of the domain events.

Interfaces

IBinaryMessage

A binary message that is being transferred over the message broker without serializing and deserializing it.

IBrokerEnvelope

Wraps the deserialized inbound or outbound message.

ICommand

A message that triggers an action.

ICommand<TResult>

A message that triggers an action with a result TResult.

IEnvelope

Wraps a message when it's being transferred over a message broker.

IEnvelope<TMessage>

Wraps a message when it's being transferred over a message broker.

IEvent

A message that notifies an event.

IInboundEnvelope

Wraps the message that is being consumed from an inbound endpoint.

IInboundEnvelope<TMessage>

Wraps the message that is being consumed from an inbound endpoint.

IIntegrationCommand

A message that is sent over the message broker to trigger an action.

IIntegrationEvent

A message that is sent over the message broker to notify an event.

IIntegrationMessage

A message that is sent over the message broker. It is further specialized as IIntegrationEvent and IIntegrationCommand.

ILazyMessageStreamEnumerable<TMessage>

Represent a future IMessageStreamEnumerable<TMessage>, that will created as soon as the first message is pushed.

IMessage

This marker interface is used to tell Silverback that the type is actually a message and enable features like automatic republishing. It is a good practice for all messages to implement this interface but it's not mandatory.