We've re­strict­ed ac­cess to https://www.atom­ikos.com/maven-repos­i­to­ry (our maven repos­i­to­ry) to cus­tomers only, so they can have easy and time­ly ac­cess to bug fix­es, main­te­nance re­leas­es and full fea­ture re­leas­es.

If you're not a cus­tomer then you have two op­tions:

• Either sub­scribe to­day to be­come one, or
• Grab our com­mu­ni­ty re­leas­es via maven cen­tral

In the near fu­ture we plan to dis­trib­ute Trans­ac­tion­sEssen­tials ex­clu­sive­ly via the cen­tral maven repo.

Ear­ly adopters want­ed! We are work­ing on some­thing rad­i­cal­ly dif­fer­ent and new in the in­dus­try, be­ing a light-weight trans­ac­tion (and BPM) mod­el for REST with the fol­low­ing char­ac­ter­is­tics:

• Guar­an­teed in­ter­op­er­abil­i­ty
• Easy and in­tu­itive to use
• No tech­nol­o­gy de­pen­den­cies, so no con­fig­u­ra­tion re­quired
• Com­pat­i­ble with the REST ar­chi­tec­tur­al con­straints

To get an idea of what it is like, con­sid­er the fol­low­ing ex­am­ple: a tel­co op­er­a­tor wants to al­low cus­tomers to ac­quire 'per­son­al­ized' phone num­bers for a fee. The process is the fol­low­ing, as­sum­ing an in­com­ing re­quest for a giv­en cus­tomer and a cho­sen phone num­ber:

1. The sys­tem checks if the num­ber is avail­able, and if so then re­serves that num­ber for some time (on be­half of the cus­tomer).
2. The cus­tomer's cred­it is checked in the billing sys­tem.
3. If OK, then the phone num­ber reser­va­tion is con­firmed and the billing is done.
4. Other­wise, the phone num­ber is re­leased again and no billing is done.

Imag­ine the BPM mod­el­ing you would need to do to han­dle all fail­ure sce­nar­ios and con­fir­ma­tion sce­nar­ios from that last 2 steps. We know from ex­pe­ri­ence that this does not scale...

In­stead, what we of­fer is a com­plete and re­li­able au­toma­tion of the con­fir­ma­tion and can­cel­la­tion steps - let­ting you fo­cus on the hap­py path of the work­flow. We do this via a ser­vice called TaaS ( TCC as a Ser­vice) and plan to of­fer a REST im­ple­men­ta­tion of that. We've pre­sent­ed this idea at the re­cent SOA sym­po­sium (the pre­sen­ta­tion can be found here) and we are look­ing for ear­ly adopters to spon­sor our ver­sion one prod­uct...

So if your SOA should be light­weight and in­volves the con­cept of reser­va­tions of busi­ness re­sources then please email us to­day to ap­ply for our ear­ly adopter pro­gram. Don't wait, be­cause be­ing a small com­pa­ny we can only do a few of these and first come means first served...

To­day we've up­dat­ed our web­site to re­flect our new busi­ness mod­el: we now only of­fer ser­vices and train­ing to sub­scribers of Ex­tremeTrans­ac­tions only...

Why did we do this? There are a few rea­sons, but here are the most im­por­tant ones:

• We've had too many dis­cus­sions with cus­tomers that want­ed ap­pli­ca­tion cer­ti­fi­ca­tion and need­ed the lat­est bug fix­es - but did not want sub­scribe to get them. The fact that they bought de­vel­op­er ac­cess (sup­port) made them feel dis­ap­point­ed when they couldn't get bug fix­es (which re­quires a full sub­scrip­tion as per our poli­cies). This was un­fair to them as well as to­wards our full sub­scribers/cus­tomers for Ex­tremeTrans­ac­tions.
• We've had to pro­duce too many cus­tom quotes for peo­ple who were not se­ri­ous about buy­ing our ser­vices in the first place - which kept us from our core busi­ness: im­prov­ing our prod­uct with great fea­tures to the ben­e­fit of both our com­mu­ni­ty and our cus­tomers. Our new mod­el makes a lot of cus­tom quotes un­nec­es­sary and ir­rel­e­vant be­cause every­thing should now be ap­par­ent from mere­ly by vis­it­ing our web shop (let us know if not).

In sum­ma­ry, we think this makes man­ag­ing ex­pec­ta­tions a lot eas­i­er and clear­er on every­body's ac­count. If you think this is un­fair then take a quick look at what the com­pe­ti­tion in open source is do­ing - you'll see that we're not be­ing un­rea­son­able here. You might also want to check with the "com­mer­cial en­ter­prise soft­ware" com­pe­ti­tion to see that their main­te­nance prices alone are an or­der of mag­ni­tude high­er than our sub­scrip­tion cost - not even count­ing their li­cense fees

Your in­put is need­ed for our re­lease plan­ning:

http://fog­bugz.atom­ikos.com/de­fault.asp?com­mu­ni­ty.6.2714.0

Thanks!

Due to a serv­er mi­gra­tion you may ex­pe­ri­enc­ing prob­lems with sup­port emails. We are work­ing to re­solve the prob­lem.

In the mean­time, thanks for your un­der­stand­ing and pa­tience.