The typ­i­cal case: dis­trib­uted trans­ac­tions with­out ap­pli­ca­tion serv­er

The vast ma­jor­i­ty of our users are re­ly­ing on Atomikos to man­age their trans­ac­tions across dis­parate back­end sys­tems with­out the need for an ap­pli­ca­tion serv­er.

So when should you con­sid­er pay­ing? That's easy: if you are ex­chang­ing mes­sages be­tween sys­tems that car­ry in­for­ma­tion that can­not eas­i­ly be re­pro­duced, or trig­gers ex­pen­sive process­es in the back­ground. Some ex­am­ples:

• Money trans­fers be­tween bank­ing sys­tems - if you lose these then you are los­ing mon­ey.
• Stock/in­ven­to­ry up­dates - if you lose those then your in­ven­to­ry man­age­ment is not re­flect­ing the real sit­u­a­tion.
• Order mes­sages: if you lose an or­der then - well - you're los­ing busi­ness.
• Sched­ul­ing mes­sages that trig­ger ex­pen­sive process­es: if these get lost (or worse, sent in­ap­pro­pri­ate­ly or twice) then you risk a lot of use­less process work.

In all of the above cas­es, you can't af­ford re­ly­ing on an un­sup­port­ed open source plat­form so I am sure you will want all the crit­i­cal bug fix­es in­clud­ed in Ex­tremeTrans­ac­tions.

Ready to try?

Down­load Trans­ac­tion­sEssen­tials: Our FREE no-appserv­er-re­quired JTA/XA

Who else uses Atomikos? Check out some of our cus­tomers!