What messaging layer to choose?

Ruby
1

Hi everybody!

I need advice on choosing messaging layer for SaaS application building.
I chose Ruby as a language, PostgreSQL as a database and OpenLaszlo as a
client layer.
And finally I should choose messaging layer. I found these layers
mentioned on one article from Web:
AMF$ RTMP, REST, SOAPWSDL, SOAPWSDL, UDDI, XML-RPC.
Maybe some of you encountered such tasks before, help me, what messaging
layer I should use?
Thanks in advance!

Sincerely,
Asset

2

On Oct 7, 2011, at 6:30 PM, Асет Орымбаев wrote:

Asset
Hi Asset,

Messaging between what ? (other apps and you , between your servers,
between client - server ) What kind of messages ? (contents and size)
How many messages do you want to be able to serve ?

Choosing the correct protocol ( which would also impact your
architecture if not define) requires a lot of detail and must people
will tell you that you should perform some prototypes on your own to see
what is best for your needs. In any case please provide more detail ( if
there aren’t any privacy issues ) and we can try to help you out :slight_smile:

( maybe its just me )

Regards,
Vicente

3

Hi Vicente,

Thanks for response.
Between client and server I suppose)) I’m newbie and don’t have a whole
concept.
I mean I don’t know about messages yet)) I can describe what I’m trying
to do.
This will online accounting service on a subscription basis (in my
country). Where people can:
create accounting documents (invoices, acts, etc.) tax reports (and send
them), reports on stuff (tax and other reports.
Also client should receive notifications about time when they have to
send reports through e-mail (maybe also by sms).
This is how I see it now.
Thanks again, will be waiting your response!

Sincerely,
Asset

07 октября 2011, 20:53 от Vicente B. Campos [email protected]:

4

On 10/07/2011 12:30 PM, Асет Орымбаев wrote:

Hi everybody!

I need advice on choosing messaging layer for SaaS application building.
I chose Ruby as a language, PostgreSQL as a database and OpenLaszlo as a client
layer.
And finally I should choose messaging layer. I found these layers mentioned on
one article from Web:
AMF$ RTMP, REST, SOAPWSDL, SOAPWSDL, UDDI, XML-RPC.
Maybe some of you encountered such tasks before, help me, what messaging layer I
should use?

As someone else asked, what do you mean by “messaging layer”? Do you
want to have multiple instances of your app communicating over some sort
of enterprise messaging system? If so, then I’d say give Qpid [1] a try.

[1] http://qpid.apache.org

5

Hi Vicente,

Also each client should have their own cabinet.

Sincerely,
Asset

07 октября 2011, 20:53 от Vicente B. Campos [email protected]:

6

Hi Vicente,

I forgot to add, I foresee that many people will use this system, maybe
tens of thousands or even more.
So I should create very stable system)))

Sincerely,
Asset

07 октября 2011, 20:53 от Vicente B. Campos [email protected]:

7

On Oct 7, 2011, at 7:20 PM, Асет Орымбаев wrote:

( maybe its just me )

Regards,
Vicente

Hi Asset,

OpenLaszlo is a DHTML generation language. From what I have seen there
is a plugin for rails to be able to use OpenLaszlo (
http://laszlo-plugin.rubyforge.org/)

Rails ( as you may now ) is a web framework for ruby and it uses HTTP (
or HTTPS if you configure ) for communication with the client side ( the
browser). It can be very scalable
or not depending on how you code the app (there are no silver bullets).
The protocols you commented on your initial email are more for app to
app communication.

Rails also allows PostgreSQL ( and Oracle, MySQL, …) so that
requirement is also covered.

Regards,
Vicente

8

Hi Vicente,

Thanks for advices!

Sincerely,
Asset

08 октября 2011, 12:05 от Vicente B. Campos [email protected]: