Feature

Transactions, SOA and Loose Coupling

How do you enforce a transactional contract among services in an SOA environment?  By focusing on the Happy Path, Atomikos resolves commonplace issues surrounding web service transactions and the demand for loose coupling. This article details the Atomikos method.

Other News

Case Study: Atomikos Delivers Lightweight Transaction Model for SCA

Transactions in SOA environments provide their own set of challenges. Managing long transactions across a series of loosely coupled components is difficult, and can impact data integrity and roll back ability. Past SOA models did not effectively address transactions, leaving implementation of transactions in SOA environments completely up to the architect.  SCA takes a different and more prescriptive approach, and specifically cites transaction support within its list of requirements. SCA incorporates transaction knowledge within its framework, allowing transactions to reliably occur across various discrete components – even when the components themselves have no transaction knowledge. In this case study , author, creator of SCA, founder of MetaForm Systems, and the mastermind behind Fabric3 Jim Marino, talks about finding Atomikos, and how Atomikos' transaction reliability and run-time guarantees are helping his customers embrace SCA and the Cloud.

UK Online TV Service Deploys Intalio Jetty with Embedded Atomikos Technology

Intalio's latest press release announces that the UK online TV service SeeSaw has deployed Jetty, which in turn embeds Atomikos TransactionsEssentials technology.  SeeSaw delivers a broad range of TV content for the UK market, and relies upon highly reliable and scalable software solutions to ensure quality service to potentially millions of viewers. Read the full press release .

Is OpenSource Atomikos Enough?

Are you looking for basic transaction support, or do you need more robust functionality including transactions over SOAP, RMI-IIOP, and patent-pending Try-Confirm/Cancel support?  Compare Atomikos open source and commercial offerings to determine the optimal product for your organization.

Container Managed Transactions for Servlets and JSP

EJB containers provide container-managed transactions (CMT) as the preferred transaction demarcation mechanism. However, the same is possible for 'simple' servlet/JSP applications that don't have access to EJB technology. This tech tip explains how.

Back to top