In any TXSeries deployment, it's a common practice to have a transaction span across multiple TXSeries regions on the same machine or across multiple machines. For example, a transaction originating from a client (say a CTG client) traverses more than a region before completing the work.
Do you feel dizzy with such transactions travelling across to multiple regions? Is a multiple hop configuration turning out to be tough to manage? Perhaps, you would like to track where the transaction originated and the peer region who... [More]