Forgot to add, read a few comments about this being an option as well: The messages are quite short, mostly 200 characters or less, max 5kByte. So I would prefer a messaging system where I can send the actual message and not just a pointer, would alleviate the need for a DB connection for everyone.
On Aug 8, 9:14 pm, Tom <[email protected]> wrote: > Good evening, > > I am a queue newbie and are completely lost in the plethora of > possibilities. My question is, what I will draft here, the best and > MOST simple way to reach my goal - and especially is beanstalk the way > to go? Any pointers really appreciated! > > Case: > I am developing a Ruby on Rails app that basically works as a message > hub for transport drivers. The system talks to the drivers, the > drivers talk to each other and the system via the system. I expect > thousands of messages a day, later a few million max a day. Messages > are externally in different formats, like twitter, xmpp, aim and SMS. > So latency is a big problem, the message turnaround is important. > Persistence is not a big problem, because once the messages are older > than a few minutes they are worthless anyway. Simplicity and easy > integration are currently key! > > Planned way to go: > My business logic runs on a full blown rails stack. This stack is > connected to a multitude of very simple, single protocol workers > (written in ruby) in their own processes via one ore more queues (in > and out). It would be ideal if the messaging solution already has > consumers that are able to convert to http/rest, xmpp etc. (RabbitMQ > seems to have at least http, but it seems like overkill to me...) > > Concrete questions: > 1.) Should I have two queues per protocol (incoming and outgoing). So > I end up having 6 queues if I use twitter, sms and xmpp? > 2.) At the beginning a distributed queue doesn't seem necesssary (ruby > should be easily able to deal with this internally) - but maybe later > - a distributed queue may be helpful? > 3.) Is beanstalk the best protocol and server to reach my goal or > should I go with a RabbitMQ/ActiveMQ or simple with a DBr solution > that simple shares an/a few internal ruby queue(s)? > > P.S: I read about the async_observer plugin: Seems like a dream come > true, because I already have a few long running methods in the system > I later would need to make asynchronous (like geocoding locations > etc.) Can this easily been done with beanstalk/async observer or am I > missing something here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
