Ask questions and see you at December, 9th, 8pm CET: http://www.ustream.tv/channel/adambien
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions.
Thank you for the super interesting http://airhacks.fm podcasts 😀
I have followup question regarding Microprofile in a Kubernetes cluster:
Is XA transactions managing a write to DB and to a MQ queue a liable solution (classic two face commit)?
Due to the volatile nature of pods the discussion at work goes something like:
XA is supported via JTA in Wildfly 18 (no surprise). But due to the volatile nature of Kubernetes pods, maybe not the right way to go.
Simplest possible flow of two face commit within a Pod / Wildfly / MicroProfile instance:
I really have trouble seeing this be a reliable solution due to that (in case of crash) the pod can respawn in a stateless manner anywhere in the cluster.
It could be that all MicroProfile instances using XA need to use PersistentVolume and PersistentVolumeClaim in order to give the JTA Transaction Manager state fullness and the ability to recover.
If my question makes any sense, could you please point me in the right direction.
Tnx in advance.