Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Re: Re: Re: Re: Re: J2EE is too complicated - why not Perl?

by eduardo (Curate)
on Dec 12, 2003 at 23:42 UTC ( #314439=note: print w/ replies, xml ) Need Help??


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

I have... across a mainframe / oracle / mssql boundry. It was not exactly the most fun thing in the world I've ever done, though I am reticent to admit (btw, I don't like java on a "personal preference" level), using Java did make it considerably easier. The mainframe vendor (IBM) already had a great many objects we could use to interface with MQ and CICS... Oracle behaved in an intelligent manner (they have too much invested in java to not at least *attempt* to behave in an intelligent manner), and the MSSQL work... actually, now that I think about it, someone else completely did that work :)

i'm not saying that it's not likely and possible that if such a framework and series of libraries existed for perl, it wouldn't be equally suited. i just *personally* have no experience with perl on that level, nor have I successfully in my googling found a vendor (or preferably vendors) that provide a perl framework with such functionality. *sigh*, what a shame.


Comment on Re: Re: Re: Re: Re: J2EE is too complicated - why not Perl?
distributed transactions
by perrin (Chancellor) on Dec 13, 2003 at 01:05 UTC
    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?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (5)
As of 2015-07-05 05:10 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (60 votes), past polls