Database Reference
In-Depth Information
By default, IBus uses the XML serialization, but it could be set directly by using the fol-
lowing:
The options for the IBus serialization are as follows:
• XmlSerialization: This is set by default, and it serializes data into an XML form.
• BinarySerialization: This is a serialization in binary form.
• BsonSerialization: This is a serialization for binary-encoded serialization for
JSON-like documents; for more information, refer to
http://codebetter.com/
• JsonSerialization: This is a JavaScript Object Notation (JSON) format; for more
information, refer to
http://msdn.microsoft.com/en-us/library/
The transport storage
We need to set the transport information using the
.UseTransport()
configured por-
tion of the IBus. This will be the transportation method that will be followed across the
bus, and remember that the endpoints that you want to communicate together must all
communicate across the transport method. In other words, a message on MSMQ and mes-
sage in SQL will not see each other. An example is already given previously, but here are
some of the following choices:
•
UseTransport<Msmq>
: You can use MSMQ transport for messages.
•
UseTransport<SqlServer>
: You can use a
SqlServer
table to queue
messages.
•
UseTransport<ActiveMQ>
: You can use ActiveMQ to queue messages.
•
UseTransport<RabbitMQ>
: You can use RabbitMQ to queue messages.
•
UseTransport<AzureServiceBus>
: You can use Azure ServiceBus; see
http://docs.particular.net/NServiceBus/windows-azure-transport
.
A sample of this
is found at
https://github.com/Particular/NServiceBus.Azure.Samples
.
