Data Bus

Although messaging systems work best with small message sizes, some scenarios require sending binary large objects (BLOBs) data along with a message (also known as a Claim Check). For this purpose, NServiceBus has a Data Bus feature to overcome the message size limitations imposed by an underlying transport.

How it works

Instead of serializing the payload along with the rest of the message, the Data Bus approach involves storing the payload in a separate location that both the sending and receiving parties can access, then putting the reference to that location in the message.

If the location is not available upon sending, the send operation will fail. When a message is received and the payload location is not available, the receive operation will fail as well, resulting in the standard NServiceBus retry behavior, possibly resulting in the message being moved to the error queue if the error could not be resolved.

Transport message size limits

Using the Data Bus is required when the message size can exceed the transport message size limit.

Enabling the data bus

See the individual data bus implementations for details on enabling and configuring the data bus.

• File Share Data Bus
• Azure Blob Storage Data Bus

Cleanup

By default, BLOBs are stored with no set expiration. If messages have a time to be received set, the data bus will pass this along to the data bus storage implementation.

Specifying data bus properties

There are two ways to specify the message properties to be sent using the data bus:

1. Using the DataBusProperty<T> type
2. Message conventions

Using DataBusProperty<T>

Set the type of the property to be sent over the data bus as DataBusProperty<byte[]>:

public class MessageWithLargePayload
{
    public string SomeProperty { get; set; }
    public DataBusProperty<byte[]> LargeBlob { get; set; }
}

Using message conventions

NServiceBus also supports defining data bus properties via a convention. This allows data properties to be sent using the data bus without using DataBusProperty<T>, thus removing the need for having a dependency on NServiceBus from the message types.

In the configuration of the endpoint include:

var conventions = endpointConfiguration.Conventions();
conventions.DefiningDataBusPropertiesAs(property =>
{
    return property.Name.EndsWith("DataBus");
});

Set the type of the property as byte[]:

public class MessageWithLargePayload
{
    public string SomeProperty { get; set; }
    public byte[] LargeBlobDataBus { get; set; }
}

Serialization

By default NServiceBus uses a BinaryFormatter to serialize and deserialize data bus properties.

Using a custom serializer

To override the data bus property serializer, create a class that implements IDataBusSerializer and add it to the dependency injection container.

Data bus attachments cleanup

The various data bus implementations each behave differently with regard to cleanup of physical attachments used to transfer data properties depending on the implementation used.

Why attachments are not removed by default

Automatically removing these attachments can cause problems in many situations. For example:

• The supported data bus implementations do not participate in distributed transactions. If the message handler throws an exception and the transaction rolls back, the delete operation on the attachment cannot be rolled back. Therefore, when the message is retried, the attachment will no longer be present causing additional problems.
• The message can be deferred so that the file will be processed later. Removing the file after deferring the message, results in a message without the corresponding file.
• Functional requirements might dictate the message to be available for a longer duration.
• If the data bus feature is used when publishing an event to multiple subscribers, neither the publisher nor any specific subscribing endpoint can determine when all subscribers have successfully processed the message allowing the file to be cleaned up.
• If message processing fails, it will be handled by the recoverability feature. This message can then be retried some period after that failure. The data bus files need to exist for that message to be re-processed correctly.

Alternatives

• Use a different transport or a different transport tier
• Message Compression: Use message body compression which works well on text-based payloads like XML and Json or any payload (text or binary) that contains repetitive data
  • Message mutator example demonstrating message body compression
• Stream-based properties: The Handling large stream properties via pipeline sample demonstrates a purely stream-based approach (rather than loading the full payload into memory) implemented by leveraging the NServiceBus pipeline.
• Binary Serializer: A binary serializer is more efficient and most serializers can be added with a few lines of code
  • Some binary serializers are maintained by the community
• Attachments: When dealing with unbounded binary payloads consider the community maintained NServiceBus.Attachments
  • Read on demand: Will only retrieve attachment data when the consumer reads it
  • Reduced Memory usage: No base64 serializer overhead resulting in a significant reduction in resource utilization
• Use any of the above in combination with compression

Other considerations

Monitoring and reliability

The storage location for data bus blobs is critical to the operation of endpoints. As such it should be as reliable as other infrastructure such as the transport or persistence. It should also be monitored for errors and be actively maintained. Since messages cannot be sent or received when the storage location is unavailable, it may be necessary to stop endpoints when maintenance tasks occur.

Auditing

The data stored in data bus blobs may be considered part of an audit record. In these cases data bus blobs should be archived alongside messages for as long as the audit record is required.