Some peo­ple will claim that REST does not need BPM be­cause it pro­vides all the se­man­tics you need.

How­ev­er, if you look be­neath the hood then it turns out that this is not ex­act­ly true: in par­tic­u­lar, if mul­ti­ple (in­de­pen­dent) REST ser­vices need to come to the same out­come then you want some­thing more...

Won­der­ing what that is? Good! It's all ex­plained in one of our lat­est pub­li­ca­tions - to learn the de­tails: just fill out this form.

En­joy!

So you're into REST and you are won­der­ing how to de­fine some kind of trans­ac­tion guar­an­tee with it...

Look no fur­ther, be­cause we have ex­act­ly what you need:

• A de­sign pat­tern
• A sim­ple, ven­dor-in­de­pen­dent REST API
• Backed by a reusable co­or­di­na­tor ser­vice if you need one (that is up to you, re­al­ly)

FREE down­load: "TCC for REST API" (API spec­i­fi­ca­tion)

PS: the tech­nol­o­gy de­scribed in this spec­i­fi­ca­tion is avail­able and can be down­loaded as part of Trans­ac­tion­sEssen­tials

This post was based on old con­tent and is no longer rel­e­vant.

Visit our Distrib­uted Trans­ac­tions Tu­to­r­i­al for equiv­a­lent con­tent.

We found this nice tu­to­r­i­al by Gonça­lo Mar­ques cov­er­ing ba­sic two-phase com­mit with Spring, Tom­cat and Atomikos.

En­joy!

PS with our lat­est Tom­cat in­te­gra­tion - avail­able to com­mer­cial sub­scribers - things are even eas­i­er

In­ter­est­ing in­de­pen­dent sur­vey: 68% uses a web con­tain­er like Tom­cat or Jet­ty.

Cred­it for the sur­vey is due to Zero Turnaround