In mod­ern Java ar­chi­tec­tures, flex­i­bil­i­ty isn’t a lux­u­ry — it’s a re­quire­ment.

Stop gam­bling with your data in­tegri­ty.

From de­bunk­ing the "XA is slow" myth to solv­ing cloud-na­tive re­cov­ery with LogCloud, we are show­ing you how to re­claim your de­vel­op­er pro­duc­tiv­i­ty and bring 100% atom­ic­i­ty to your mi­croser­vices.

If you are build­ing mi­croser­vices, you have prob­a­bly heard of the Saga pat­tern. Maybe you are even us­ing it. After all, it is the de­fault an­swer you will find on Stack Over­flow and in most con­fer­ence talks when peo­ple ask: How do I man­age dis­trib­uted trans­ac­tions?

Syn­chro­nous mi­croser­vices look great on pa­per.

They are easy to read, easy to de­bug, and they map per­fect­ly to how we think: “I send a re­quest, I get a re­ply.” No sur­pris­es, right?

Ex­cept when things go wrong. Which in dis­trib­uted sys­tems is most of the time.

The bad guys are try­ing to get into your projects. What can you do to avoid pulling in bad code?