Welcome to Atomikos
Mon, 17 Nov 2014 18:27:53 +0000 atomikos
A few weeks back we’ve been sending around this poll via our newsletter subscriber base. We got a lot of answers so I will not go into every single one of them (and we can’t send individual replies, BTW, because the survey was anonymous). However, here is a distillation of the results, and our comments / questions to each:
Business model: some respondents suggested we look into a new business model like JBoss, for instance. We don’t really understand why, because what we are doing is about the same thing as what Red Hat is doing? We’re curious to learn though, if anybody wants to clarify…
Integrations: a lot of people requested more built-in integration with third-party platforms. We’re certainly doing that: we’ve recently added Tomcat and are working on more things to come… Thanks for that!
Documentation: We always need more documentation. Somebody also suggested that we restructure our existing docs and offered to help. If you are that person, please email us (plenty of contact addresses on our website). Thanks!
Performance: We should do more benchmarking and publish / compare the results. That is certainly true, but we found that it depends so much on your configuration (not ours) that it is hard to come to a general conclusion. It just depends…
Again, we were not able to contact individual respondents so our interpretation and conclusion could be wrong. If that is the case, and you feel misunderstood (or just want to help) then please get in touch via our website.
Tue, 30 Sep 2014 19:54:43 +0000 GuyPardon
Microservices are all about splitting up responsibilities of your domain’s bounded context into several HTTP-like services, deployed independently. So essentially it means splitting up process boundaries across different services - away from the monolith…
What is the consequence for your business transactions? In some (though not all) cases you may need some notion of transaction management but you can’t resort to XA or classical distributed transactions in the REST world…
So what are your options? Our newest API, TCC for REST, allows light-weight BPM and transaction management across independent REST services. Interested in learning all about it? Find out for yourself here (requires registration).
Tue, 30 Sep 2014 14:33:39 +0000 GuyPardon
Scaling applications to the web and the cloud - combined with continuous deployment automation practices - is not easy. The current rigid and oversized infrastructure platforms don’t help here.
So it’s time for something different: discover our increasingly popular “no-appserver-paradigm”, enabling you to use all of the enterprise features without the heavy platform burden…
Download the full article here! (requires registration)
Sun, 28 Sep 2014 19:14:22 +0000 GuyPardon
Some people will claim that REST does not need BPM because it provides all the semantics you need.
However, if you look beneath the hood then it turns out that this is not exactly true: in particular, if multiple (independent) REST services need to come to the same outcome then you want something more…
Wondering what that is? Good! It’s all explained in one of our latest publications - to learn the details: just fill out this form.
Sun, 28 Sep 2014 19:07:29 +0000 GuyPardon
So you’re into REST and you are wondering how to define some kind of transaction guarantee with it…
Look no further, because we have exactly what you need:
Find out for yourself here! (requires registration)
If you have any questions or remarks, we’d love to hear about it…