How to avoid los­ing trans­ac­tion logs when your pod crash­es

Pod crashed? Trans­ac­tion logs lost? Read this...

If you're us­ing Ku­ber­netes or OpenShift then you're prob­a­bly de­ploy­ing pods to your pro­duc­tion cloud. A crash of a pod (ei­ther by ac­ci­dent or will­ing­ly killing it) can eas­i­ly lead to loss of the trans­ac­tion log files that were stored in it. This can lead to pend­ing trans­ac­tions and, worst case, cor­rupt­ed data in your back­end re­sources.

To avoid this, we have de­signed an "ex­ter­nal" stor­age mech­a­nism for trans­ac­tion logs. It is called LogCloud and stores trans­ac­tion logs in a re­la­tion­al DBMS of your choice. This way, when­ev­er you lose a pod you still keep its trans­ac­tion log data - and re­cov­ery will cleanup in the back­ground. It's what we call self-heal­ing trans­ac­tions for the cloud.

Want to try this out? We of­fer a free tri­al of Ex­tremeTrans­ac­tions to set this up for you.

Free Tr­i­al