TCP Transport

Note! This transport works by sending traffic directly via sockets and may not be acceptable in your IT department policies. It is load tested and is based on the older LightningQueues project that was happily used in high volume systems, so we feel like it's plenty robust.

Lightweight, fire and forget

The TCP transport without durability is meant for scenarios where message delivery speed and throughput is important and guaranteed delivery is not required. We originally conceived this option as a .Net equivalent to ZeroMQ.

To set up a Jasper application to listen for incoming and outgoing messages through the TCP transport in the lightweight mode, see this example:

public class LightweightTransportApp : JasperOptions
    public LightweightTransportApp()
        // Set up a listener (this is optional)

        Endpoints.Publish(x =>
                .ToServerAndPort("remoteserver", 2201);

In the case of a failure to send a message, the lightweight transport will retry to send the message a few times (3 is the default), but the message will be permanently discarded in about 10 seconds if it is unsuccessful. The lightweight transport is useful for control messages or messages that have a very limited value in terms of time. My shop uses this transport for frequent status update messages that are very quickly obsolete.

Durable TCP Messaging

First, see Durable Messaging and Command Processing about how message durability is enabled and functions within Jasper.

The TCP transport can be used durably as both listener or sender. To configure a durable TCP listener, use one of these options:

public class DurableTransportApp : JasperOptions
    public DurableTransportApp()
            .ToServerAndPort("server1", 2201)

            // This applies the store and forward persistence
            // to the outgoing message

        // Set up a listener (this is optional)

            // This applies the message persistence
            // to the incoming endpoint such that incoming
            // messages are first saved to the application
            // database before attempting to handle the
            // incoming message


Uri Pattern

The Uri structure for this transport is tcp://[server]:[port] for fire and forget, and tcp://[server]:[port]/durable if the endpoint should be durable.