How to avoid losing transaction logs when your pod crashes

Pod crashed? Transaction logs lost? Read this…

If you're using Kubernetes or OpenShift then you're probably deploying pods to your production cloud. A crash of a pod (either by accident or willingly killing it) can easily lead to loss of the transaction log files that were stored in it. This can lead to pending transactions and, worst case, corrupted data in your backend resources.

To avoid this, we have designed an "external" storage mechanism for transaction logs. It is called LogCloud and stores transaction logs in a relational DBMS of your choice. This way, whenever you lose a pod you still keep its transaction log data - and recovery will cleanup in the background. It's what we call self-healing transactions for the cloud.

Want to try this out? We offer a free trial of ExtremeTransactions to set this up for you.

Free Trial