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

[SIMATIC Michel]

Hi George,

About your fear that RabbitMQ may be overkill for your needs, I would 
answer that RabbitMQ saves you a lot of time, especially when you start 
dealing with "rare" cases (which turn to be frequent in production), 
that is for example disconnections...

FYI, with colleagues, we have developed, on top of RabbitMQ, a layer 
called ZebroGaMQ (https://github.com/simatic/ZebroGaMQ). Here are its 
features:
- Creation and join of game sessions,
- Sending messages to a single player or to all players,
- Client-server or peer-to-peer game logic,
- Server coding done in Python,
- Client coding done in Java or Javascript,
- LGPL license.
Maybe it can help you?

Best regards,

Michel


Le 18/11/2012 13:00, rabbitmq-discuss-request at lists.rabbitmq.com a écrit :
> Message: 5
> Date: Sat, 17 Nov 2012 07:55:32 -0800
> From: Jerry Kuch<jerryk at rbcon.com>
> Subject: Re: [rabbitmq-discuss] is RabbitMQ a good choice for a
> 	small-scale multiplayer game server?
> To: Discussions about RabbitMQ<rabbitmq-discuss at lists.rabbitmq.com>
> Cc:rabbitmq-discuss at googlegroups.com
> Message-ID:
> 	<CAE0Sz=w_m5JJBC6UbfBG-SHpvyx68N+9dU1nSnE0FQZdZ11nGA at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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
>> >