You need to really analyze your requirements. Why do you want/need a message queue and not a database? Do you need to support message durability, clustering of

You need to really analyze your requirements. Why do you want/need a message queue and not a database? Do you need to support message durability, clustering of nodes, nodes in different geographical regions, topical subscriptions, what kind of routing concerns, technology support (do you want/need to write your own client to interface with the message queue? hopfully not...if you're using a particular language you just might though), protocol support (do you need amqp support), etc.? Personally I like RabbitMQ.