[rabbitmq-discuss] is RabbitMQ a good choice for a small-scale multiplayer game server?

[Jerry Kuch]

Hi, George:

Rabbit's quite flexible in letting you start small, and the investment of
time in putting up a simple deployment is a small part of an afternoon.
 Understanding its full semantics and the details of the various delivery
guarantees you can ask for takes a bit longer, but can happen concurrently
with the build out of your application.

I'd suggest giving it a try.  Read the Rabbit tutorials on the website if
you haven't already, pick up the Rabbit book for bed time reading, and map
out the sorts of message flows your gaming app will require.  In many ways
they may turn out to be one of the simpler parts of it once you've adopted
Rabbit...

Best regards,
Jerry

On Fri, Nov 16, 2012 at 6:04 PM, George Oliver <georgeolivergo at gmail.com>wrote:

> hi, I'm evaluating design choices while writing a game server. As I don't
> have a lot of experience with distributed systems I'd appreciate advice
> from you all.
>
> My project is a mud (real-time multiplayer text game) where you can write
> the game logic in different programming languages; for example, the
> movement system in Python and the combat system in Ruby. These systems
> communicate via message over a socket with the central server which manages
> player connections.
>
> I like the idea of using message queues and RabbitMQ looks like a
> particularly nice project, but I'm concerned it might be overkill for my
> needs. I'm familiar with the notes at
> http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Notes but their
> use case is much different than my own. I don't anticipate more than 500
> player connections and 50 game logic processes (though each logic process
> could have, say, 100 queues). On the other hand I'll need to find solutions
> for some of what RMQ does anyway.
>
> Do you think I'm setting myself up for trouble by bringing in what seems
> like a big framework for this kind of project?
>
>
> thanks, George
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121117/1d3ac50e/attachment.htm>