Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

distributed transactions

by perrin (Chancellor)
on Dec 13, 2003 at 01:05 UTC ( #314445=note: print w/replies, xml ) Need Help??

in reply to Re: Re: Re: Re: Re: J2EE is too complicated - why not Perl?
in thread J2EE is too complicated - why not Perl?

If I had to do this in Perl, I would look at what the database vendors have to offer. Oracle and IBM both sell products for two-phase commit across multiple databases from different vendors. They also both implement the XA standard.

Frankly, it doesn't sound that hard to build a very basic transaction monitor that would do two-phase commit across XA databases, probably tracking state with a local transaction-capable database like SQLite. The thing is, it's probably not worth the trouble to build it. There is just so little call for this sort of thing in real-world applications. Most companies are trying to do simpler things, like basic replication. When something comes along that could conceivably be done with two-phase commit, even the DBAs typically choose to go with something less safe but much simpler. I suspect the main customers for distributed transactions are the financial industry.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://314445]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (3)
As of 2016-10-28 06:42 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (375 votes). Check out past polls.