TCC for trans­ac­tion man­age­ment across mi­croser­vices

Mi­croser­vices are all about split­ting up re­spon­si­bil­i­ties of your do­main's bound­ed con­text into sev­er­al HTTP-like ser­vices, de­ployed in­de­pen­dent­ly. So es­sen­tial­ly it means split­ting up process bound­aries across dif­fer­ent ser­vices - away from the mono­lith...

What is the con­se­quence for your busi­ness trans­ac­tions? In some (though not all) cas­es you may need some no­tion of trans­ac­tion man­age­ment but you can't re­sort to XA or clas­si­cal dis­trib­uted trans­ac­tions in the REST world...

So what are your op­tions? Our newest API, TCC for REST, al­lows light-weight BPM and trans­ac­tion man­age­ment across in­de­pen­dent REST ser­vices. In­ter­est­ed in learn­ing all about it? Find out for your­self here.

Down­load whitepa­per "TCC for REST"