Liberate Your Project With Message Queues.

If your system has big chunky flows of data, then it probably needs to be asynchronous. If it needs to be asynchronous then it probably needs more than one main process. If it needs more than one main process then it should probably be using message queues. You can start right here. Advanced Message Queueing Protocol (AMQP) makes that easy. RabbitMQ is an open-source AMQP implementation that's reliable and implemented everywhere, so we'll go with that. If you're developing an application that fits the chunky-data model, you'll want to know about AMQP and the Rabbit implementation; they're platform-agnostic and language-agnostic. You will learn what kinds of systems need message queues, what message queues can do for you, how to create a clean message queue architecture, how to think about performance, and where the security hazards are. After you attend this session, your applications won't be able to walk and chew gum at the same time—but they'll reliably outsource both tasks to the Walking task queue and the Chewing Gum task queue, and you will look like a genius.