Component: NServiceBus
NuGet Package NServiceBus (6.x)
Standard support for version 6.x of NServiceBus has expired. For more information see our Support Policy.

NServiceBus takes instances of .NET objects (messages, events, and commands) and sends/receives them over a specified transport. As part of this process, the object must be serialized and deserialized. NServiceBus achieves this using serializers.

When transitioning to a new serializer, messages that are currently 'in-flight' are formatted using the previous serialization format. This includes saga timeout and deferred/delayed messages via timeout persistence.

It's possible to transition to another serialization format while still remaining compatible with messages in-flight that used the previous serialization format. This is accomplished by adding the previous serialization format as an additional deserializer, which is supported in NServiceBus versions 6 and above.

The Newtonsoft JSON Serializer provides an effective general-purpose serializer appropriate for most use cases based on the ubiquitous Json.NET package. The Newtonsoft package provides a good combination of compactness, human readability, and performance. Other serializers are supported in order to enable specific performance or integration requirements.

Supported serializers

Configuring a serializer

A serializer can be configured using the endpointConfiguration.UseSerialization API. Refer to the dedicated documentation pages for each available serializer for more information about the specific configuration.

The same serializer must be used by the sending endpoint to serialize messages and by the receiving endpoint to deserialize them, unless additional deserializers are specified.

Using the default serializer

The default serializer used in NServiceBus projects is the custom XmlSerializer. Unless explicitly configured otherwise, NServiceBus will use XmlSerializer for serializing and deserializing all messages.

Using a custom serializer

Besides the officially supported and community maintained serializers, it is also possible to implement and register a custom serializer.

Specifying additional deserializers

To support sending and receiving messages between endpoints using different serializers, additional deserialization capability may be specified. It is possible to register additional deserializers to process incoming messages. Additionally, if a deserializer requires custom settings, they can be provided during its registration.

// Configures new default serialization
var mySerializer = endpointConfiguration.UseSerialization<MyCustomSerializerDefinition>();
// Configures additional deserializer, like the previous (default) serializer to be compatible with in-flight messages.
When using multiple deserializers make sure that there's only one type registered per given ContentType.

Immutable message types

It is possible to use immutable types as messages. NServiceBus does not restrict this; It depends on the chosen serializer implementation if it supports deserializing to non public properties and/or using non-default constructors to initialize types.

On the wire it makes no difference if mutable or immutable message types are used.

For example, the Newtonsoft JSON Serializer by default supports immutable messages types.


Related Articles

Last modified