Ruby/Perl: tight integration

Hello,

I’m planning to write a system consisting of a supervise process (which
I want to write in Ruby) and several transaction processes (written in
Perl due to library issues). I have spent some time now, looking at Rinn,
but it doesn’t support long long and all in all, it doesn’t seem like
something you’d use for a production system yet.

Other alternatives seems to be SOAP og XML-RPC; however I am a little
concerned about the performance of XML based solutions; the supervise
process needs to scale to about 80 operations/second, with bursts of
twice that.

Does anyone have practical experience with the performance of SOAP og
XML-RPC for Ruby? Or know of viable alternatives?

All help appreciated!

···


I’ve seen things you people wouldn’t believe. Attack ships on fire off
the shores of the Nonestic Ocean. I watched magic blunderbusses flash
and glitter in the dark near Glindea’s Palace. All those moments will
be lost in time, like tears in rain. Time to die…

Maybe you should consider a REST approach:

http://internet.conveyor.com/RESTwiki/moin.cgi/FrontPage
http://groups.yahoo.com/group/rest-discuss/
http://www.xml.com/lpt/a/2002/02/06/rest.html
http://www.xml.com/lpt/a/2002/02/20/rest.html

It is faster, simpler and more flexible than SOAP and XML-RPC.

Cheers,

Erik.

Bjørn Nordbø wrote:

···

Hello,

I’m planning to write a system consisting of a supervise process (which
I want to write in Ruby) and several transaction processes (written in
Perl due to library issues). I have spent some time now, looking at Rinn,
but it doesn’t support long long and all in all, it doesn’t seem like
something you’d use for a production system yet.

Other alternatives seems to be SOAP og XML-RPC; however I am a little
concerned about the performance of XML based solutions; the supervise
process needs to scale to about 80 operations/second, with bursts of
twice that.

Does anyone have practical experience with the performance of SOAP og
XML-RPC for Ruby? Or know of viable alternatives?

All help appreciated!

In article Ttv39.1735$0p1.20014@news2.ulv.nextra.no,

Hello,

I’m planning to write a system consisting of a supervise process (which
I want to write in Ruby) and several transaction processes (written in
Perl due to library issues). I have spent some time now, looking at Rinn,
but it doesn’t support long long and all in all, it doesn’t seem like
something you’d use for a production system yet.

Other alternatives seems to be SOAP og XML-RPC; however I am a little
concerned about the performance of XML based solutions; the supervise
process needs to scale to about 80 operations/second, with bursts of
twice that.

    • Hmm, that’s pretty hefty for any scripted server to deal with
      on a single processor. It certainly can be done, but you might
      have to write your own protocol to get this performance.

Does anyone have practical experience with the performance of SOAP og
XML-RPC for Ruby? Or know of viable alternatives?

    • If you’re designing your own protocol for this you might want
      to look at BEEP. It’s still XML, but has less overhead than
      either SOAP or XML-RPC. Unfortunately, the ruby implementation
      seems to be mostly vaporware at this point.
    • Booker C. Bense
···

Bjørn Nordbø bn@strangedays.no wrote:

bbense+comp.lang.ruby.Aug.05.02@telemark.stanford.edu

In article Ttv39.1735$0p1.20014@news2.ulv.nextra.no,

Other alternatives seems to be SOAP og XML-RPC; however I am a little
concerned about the performance of XML based solutions; the supervise
process needs to scale to about 80 operations/second, with bursts of
twice that.

    • Hmm, that’s pretty hefty for any scripted server to deal with
      on a single processor. It certainly can be done, but you might
      have to write your own protocol to get this performance.

Actually, I do have an option of writing a multithreaded server and
distributing the load over several CPUs. However this would defeat
my idea of using XML-RPC or similiar to simplify the server.

Does anyone have practical experience with the performance of SOAP og
XML-RPC for Ruby? Or know of viable alternatives?

    • If you’re designing your own protocol for this you might want
      to look at BEEP. It’s still XML, but has less overhead than
      either SOAP or XML-RPC. Unfortunately, the ruby implementation
      seems to be mostly vaporware at this point.

BEEP is a new one, but without a Ruby implementation it’s pretty much
useless. I don’t have the time or knowledge to implement a protocol
library yet; this is my first large Ruby project.

Thanks for your answers!

···

Bjørn Nordbø bn@strangedays.no wrote:


I’ve seen things you people wouldn’t believe. Attack ships on fire off
the shores of the Nonestic Ocean. I watched magic blunderbusses flash
and glitter in the dark near Glindea’s Palace. All those moments will
be lost in time, like tears in rain. Time to die…

Interesting; I’ll have a closer look at this. Thanks!

···

Erik Terpstra erik@solidcode.net wrote:

Maybe you should consider a REST approach:

(…)

It is faster, simpler and more flexible than SOAP and XML-RPC.


I’ve seen things you people wouldn’t believe. Attack ships on fire off
the shores of the Nonestic Ocean. I watched magic blunderbusses flash
and glitter in the dark near Glindea’s Palace. All those moments will
be lost in time, like tears in rain. Time to die…