Feature - Send-Via / TransferSender to send messages across entities in a transaction

[nemakam]

Description

This feature lets a user send messages across entities in a single transaction.

A single transaction cannot theoretically span across entities. So as to support cross-entity transaction, you can now send a message to a destination-queue via another queue. The transaction will be performed on the via-queue, and once successful, the message will be forwarded/transferred to its intended destination.
Resolves #423

Sample:

var viaQueueSender = new MessageSender(connection, viaQueueName);
var viaQueueReceiver = new MessageReceiver(connection, viaQueueName);
var destinationViaSender = new MessageSender(connection, destinationQueueName, viaQueueName);

var message1 = new Message(body) { MessageId = "1", PartitionKey = "pk1" };
var message2 = new Message(body) { MessageId = "2", PartitionKey = "pk2", ViaPartitionKey = "pk1" };

await viaQueueSender.SendAsync(message1);
var receivedMessage = await viaQueueReceiver.ReceiveAsync();

using (new TransactionScope(TransactionScopeAsyncFlowOption.Enabled))
{
	await viaQueueReceiver.CompleteAsync(receivedMessage.SystemProperties.LockToken);
	await destinationViaSender.SendAsync(message2);
}

In the above example, operations on both message1 and message2 (intended for different entities) are being performed within the same entity (i.e., the via-queue)

[SeanFeldman]

Should exception message be more specific as per why it's not supported? There are two constraints, send-via and transaction.

[SeanFeldman]

@nemakam while waiting for @binzywu's review, should the test on .NET Standard be addressed?

[nemakam]

@SeanFeldman
This requires service side changes that are yet to be deployed. The send-via test will fail meanwhile. And once a test fails, it drags down other tests as well as the queue is reused.
That's why I've put the 'onhold' tag :)

[SeanFeldman]

We need a patience-sean tag 😆

[nemakam]

nemakam added patience-sean label 5 minutes ago

[SeanFeldman]

Epic! 😂

[SeanFeldman]

@nemakam any updates? Thanks.

[nemakam]

@SeanFeldman
ETA - for preview build - a week or so. We are still waiting for the release to finish.
Then once internal long running tests pass, we can open it up. Needs couple of days for this as well.