Early adopters wanted! We are working on something radically different and new in the industry, being a light-weight transaction (and BPM) model for REST with the following characteristics:

• Guaranteed interoperability
• Easy and intuitive to use
• No technology dependencies, so no configuration required
• Compatible with the REST architectural constraints

To get an idea of what it is like, consider the following example: a telco operator wants to allow customers to acquire 'personalized' phone numbers for a fee. The process is the following, assuming an incoming request for a given customer and a chosen phone number:

1. The system checks if the number is available, and if so then reserves that number for some time (on behalf of the customer).
2. The customer's credit is checked in the billing system.
3. If OK, then the phone number reservation is confirmed and the billing is done.
4. Otherwise, the phone number is released again and no billing is done.

Imagine the BPM modeling you would need to do to handle all failure scenarios and confirmation scenarios from that last 2 steps. We know from experience that this does not scale…

Instead, what we offer is a complete and reliable automation of the confirmation and cancellation steps - letting you focus on the happy path of the workflow. We do this via a service called TaaS ( TCC as a Service) and plan to offer a REST implementation of that. We've presented this idea at the recent SOA symposium (the presentation can be found here) and we are looking for early adopters to sponsor our version one product…

So if your SOA should be lightweight and involves the concept of reservations of business resources then please email us today to apply for our early adopter program. Don't wait, because being a small company we can only do a few of these and first come means first served…

Today we've updated our website to reflect our new business model: we now only offer services and training to subscribers of ExtremeTransactions only…

Why did we do this? There are a few reasons, but here are the most important ones:

• We've had too many discussions with customers that wanted application certification and needed the latest bug fixes - but did not want subscribe to get them. The fact that they bought developer access (support) made them feel disappointed when they couldn't get bug fixes (which requires a full subscription as per our policies). This was unfair to them as well as towards our full subscribers/customers for ExtremeTransactions.
• We've had to produce too many custom quotes for people who were not serious about buying our services in the first place - which kept us from our core business: improving our product with great features to the benefit of both our community and our customers. Our new model makes a lot of custom quotes unnecessary and irrelevant because everything should now be apparent from merely by visiting our web shop (let us know if not).

In summary, we think this makes managing expectations a lot easier and clearer on everybody's account. If you think this is unfair then take a quick look at what the competition in open source is doing - you'll see that we're not being unreasonable here. You might also want to check with the "commercial enterprise software" competition to see that their maintenance prices alone are an order of magnitude higher than our subscription cost - not even counting their license fees

Your input is needed for our release planning:

http://fogbugz.atomikos.com/default.asp?community.6.2714.0

Thanks!

Due to a server migration you may experiencing problems with support emails. We are working to resolve the problem.

In the meantime, thanks for your understanding and patience.

Best wishes for the new year to all of you, from all of us!

Cheers