Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

Using Perl vs Java with MQSeries

by wileykt (Acolyte)
on Nov 26, 2001 at 20:52 UTC ( #127578=perlquestion: print w/replies, xml ) Need Help??

wileykt has asked for the wisdom of the Perl Monks concerning the following question:

I need opinions from anyone that's programmed applications to work with IBM's MQSeries.
I'm aware that both perl and java work with the api provided by MQ. What I want to know is advice on which language to use to get and put messages on the queue.
These messages I'll be getting and putting on the queue will not be big, but they will be coming and going at a rate of 150/hour. There will be one big file of about 300,000 bytes going once/day and the rest will be about 500 bytes/file.
Any opinions are welcome.

Replies are listed 'Best First'.
Re: Using Perl vs Java with MQSeries
by ask (Pilgrim) on Nov 26, 2001 at 21:00 UTC
    Uh, did you really mean 150/hour? If so, then performance will not be an issue with either language, even if the API is braindead with one of them (which I doubt).

    Use whatever language fits in best with the rest of your system or application.

     - ask

    ask bjoern hansen,   !try; do();
      I realize that this is a very old post, but I'll give my 0.2c anyway...

      The only reason I would use Java over Perl is if my MQ Server requires a certain userID to be used for security reasons. With Perl and C, the userID of the client is passed on to the server and to the best of my knowledge, there's no getting around that. With Java, you can specify the userID of your liking.

      Apart from that nuisance, I found that it's very easy to work with MQSeries through Perl and posted a write-up about it at
Re: Using Perl vs Java with MQSeries
by perrin (Chancellor) on Nov 26, 2001 at 21:23 UTC
    There's a project where I work using MQSeries from Java. It is dog slow -- not because of MQSeries, but because of the design of the messages and the XML parsing involved in the Java code. The moral of this story is that it makes no difference which one you use as long as you pick a tool that you understand and can design well for.
Re: Using Perl vs Java with MQSeries
by rje (Deacon) on Nov 27, 2001 at 01:35 UTC
    In your case, I would recommend Java over perl for these

    (1) Its strong typing may coerce developers to maintain
    a somewhat more maintainable design than perl.

    (2) Java trades away power for readability; it's easy to
    write horrible Java, but it's even easier to write horrible

    (3) Typical 3rd-generation logic constructs are expected to
    be used in Java. There's usually only one way to do it in
    Java. This leaves fewer surprises for the maintainer. That
    means people who aren't as familiar with Java can't do as
    much damage to the program as a perl novice to a perl script.

    If you don't need perl's power, by all means, use Java!

    Be warned, however: automation and data processing are fun
    in perl, while in Java they can be an absolute headache.

      This is a strange post. None of the reasons you give for using Java relate to the question (MQSeries) specifically; they're just general complaints about Perl, and they border on FUD. Many of us have written large systems in Perl, and found them as maintainable as any Java code.

      There's nothing wrong with criticizing Perl and people do it here all the time. However, try to make your critiques on-topic for the question you are answering.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://127578]
Approved by root
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (2)
As of 2022-05-23 03:25 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (81 votes). Check out past polls.