This example code is part of a blog post on the Codit blog about improving BizTalk performance by bypassing the BizTalk MessageBox with the help of Redis cache and a WCF IOperationInvoker.You can find the blogpost here.

The RedisCacheClient has the following NuGet Dependencies:

• StackExchange.Redis.StrongName

• Newtonsoft.Json

To use the RedisCacheClient you'll have to update the ConnectionString fields (these are here only for demo-purposes), we recommend to abstract these away from the client's implementation.

Write-Operations will be done to the "master", Read-Operations will be done to the "slave". We trust Redis to do the replication of this data on multi-instance environments.

More information about configuring Redis for master/slave configuration & replication can be found here.

Redis is a key-value store, to ease programming against it and to avoid typos. We introduced typed cache keys this allows us to re-use cache keys without having to worry about keeping strings up-to-date.

An example of a cachekey

public class TestCacheKey : ICacheKey
{
	public TestCacheKey(string parameter)
    {
        _name = string.Format("TestCacheKey:{0}", parameter);
    }

    private readonly string _name; 
    public string Name
    {
        get
        {
            return _name;
        }
    }
}

This is how the values are stored in Redis:

To write a value, create an instance of the RedisCacheClient, and as parameters pass a typed cache key, a value and an optional time-to-live.

var client = new RedisCacheClient();
var success = client.Write(new YourCacheKey("Codit"), true, TimeSpan.FromMinutes(15));

To read a value with the client, you only need to have a cacheKey

var client = new RedisCacheClient();
var cachedValue = _cacheClient.Read<bool>(new YourCacheKey("Codit"));

The return value implements the "MayBe principle", therefor you can check in advance if there was an acutal value found. This reads easier than having null check's.

if (cachedValue.IsPresent)
{
   // do something with cachedValue.Value
}

The IOperationInvoker is the last step before calling the actual implementation of your service, here you have the power of skipping the implementation and returning a custom message.

You can adapt the following method to have your custom decision on continuing the service call or not.

 public Task<object> InvokeOperationAsync(object instance, object[] inputs, object state)

The example code excludes retrieving the OrganisationId from the As4 Pull request, and creation of the return message. If you want to know more about As4, the Codit blog has a series As4 For Dummies

Warning: Once you read a message, the status is set to Read and cannot be read afterwards. The only solution for this is copying the message to a new message.

This method investigates the stream of the receive message, and searches for a organisationId, if a Id is found in the message, the Cache is checked. If the cache has a positive value, a new Output Message is created.

private Message GetOutputMessageForInputMessageStream(Stream messageStream)
{
    Message outputMessage = null;
    
    var organisationId = GetOrganisationId(messageStream);
    
    var cachedValue = _cacheClient.Read<bool>(new NoMessagesAvailableCacheKey(organisationId));
    
    if (cachedValue.IsPresent && cachedValue.Value)
    {
	    // Create As4 Warning Message (EmptyMessagePartitionChannel) - for demo purposes this is removed.
	    var as4MessageStream = new MemoryStream();
    }
    
    return outputMessage;
}

If no Output message is created, the current Operation is triggered to continue to the implementation.

if (outputMessage == null)
{
    var capturedOperationContext = OperationContext.Current;
    return Task<object>.Factory.StartNew(() =>
    {
        OperationContext.Current = capturedOperationContext;
        var begin = _innerInvoker.InvokeBegin(instance, inputs, null, state);
        object[] o;

        return _innerInvoker.InvokeEnd(instance, out o, begin);
    });
}

If there is a output message created, this message is returned and the service implementation is skipped.

 return Task.FromResult((object)outputMessage);

Steps to be taken to host this behavior in BizTalk:

• GAC the signed dll.
• Add the WCF behavior to the machine.config
• Add the behavior to your WCF receive port.

• https://github.com/uglide/RedisDesktopManager
• https://github.com/StackExchange/StackExchange.Redis
• https://github.com/JamesNK/Newtonsoft.Json