Abstract: Techniques for transaction tracking for a high availability architecture are described herein. An aspect includes receiving a first request from a client, the first request corresponding to a start of a transaction having transaction affinity. Another aspect includes, based on receiving the first request from the client, generating a transaction tracking token. Another aspect includes sending the first request with the transaction tracking token to a gateway. Another aspect includes receiving a first response corresponding to the first request from the gateway, the first response including middleware instance information corresponding to a middleware instance, wherein a plurality of subsequent requests from the client corresponding to the transaction are processed by the middleware instance corresponding to the middleware instance information.

Abstract: Inflight transactions having predictable pod failure in distributed computing environments are managed by integrating a transaction manager into pods having containers running applications in a distributed computing environment, wherein the transaction manager records a transaction log having data indicative of historical pod failure. A pod health check that is also integrated into the pods determines predictive pod failure scenarios from the data of historical pod failure in the transaction log. Pod health can be tracked using the pod health checker by matching the predictive pod failure scenarios to transaction calls. Calls may be sent to a load balancer for recovery of pod failure for transaction calling match the predictive pod failure scenarios. Pods can be configured recover for the predictive pod failure.

Abstract: Techniques for transaction tracking for a high availability architecture are described herein. An aspect includes receiving a first request from a client, the first request corresponding to a start of a transaction having transaction affinity. Another aspect includes, based on receiving the first request from the client, generating a transaction tracking token. Another aspect includes sending the first request with the transaction tracking token to a gateway. Another aspect includes receiving a first response corresponding to the first request from the gateway, the first response including middleware instance information corresponding to a middleware instance, wherein a plurality of subsequent requests from the client corresponding to the transaction are processed by the middleware instance corresponding to the middleware instance information.

Abstract: Techniques for handling transactions are provided. A first transaction is received at an application system of a distributed system. The first transaction is completed, where completing the first transaction comprises writing a record to a queue. A response is generated by an application resource monitor (ARM) of the application system, where the response identifies the record and the application system. The response is transmitted to a transaction distribution system, where the transaction distribution system distributes transactions among application systems in the distributed system. A second transaction is received at the application system. Upon determining that the second transaction is a trigger transaction, the ARM determines a plurality of records that are associated with the second transaction, where the plurality of records includes the record. The ARM retrieves the record from the queue, and completes the second transaction based at least in part on the record.

Abstract: Techniques for handling transactions are provided. A first transaction is received at an application system of a distributed system. The first transaction is completed, where completing the first transaction comprises writing a record to a queue. A response is generated by an application resource monitor (ARM) of the application system, where the response identifies the record and the application system. The response is transmitted to a transaction distribution system, where the transaction distribution system distributes transactions among application systems in the distributed system. A second transaction is received at the application system. Upon determining that the second transaction is a trigger transaction, the ARM determines a plurality of records that are associated with the second transaction, where the plurality of records includes the record. The ARM retrieves the record from the queue, and completes the second transaction based at least in part on the record.