Beginning to Design for Scale with RabbitMQ

gistfile1.txt

Edit: Changed description per edunham

Title: Beginning to Design for Scale with RabbitMQ
Type: Regular (1 hour including Q&A)

Description (479 of 500 chars):
When your app outgrows a single server, you begin to encounter logjams,
queues filling up, and other problems of scale. Code becomes more
complicated.

In this talk we look at distributed processing at InboxDollars.com as we scale
data collection from 50K views to 2M views/day. We focus only on the PHP back
end, from the PHP developers' perspective. You will take away some of our
lessons learned, and better understand what questions you need to answer in
scaling up your app.

Additional Information:
1. I am a new PHP speaker. However, I used to teach Cray Supercomputer operating
system internals (assembly and octal) as a Senior Instructor for Cray Research
Software Training.

2. This proposal is exclusive to PHP World.

3. I have articles in PHP Architect May, June, July 2016.

To whomever reviews this gist: My sincere thanks.

• Well done specifying the target audience and scope of the talk!
• "Not all will go well" might be more compelling as a specific list: "Configurations will get harder to manage, interesting new race conditions appear, and rate limits get rapidly exceeded" or whatever's applicable, to get the reader identifying with the specific problems that you'll offer solutions to. It looks like you're super close to your character limit, so maybe replace lines 5 and 6 with something like "when your app outgrows a single server, you begin to encounter <problem>, <problem>, and other problems of scale"
• Can you give numbers in line 10? for instance, "as we scaled from tens to thousands of customers" or something? Considering the character limit, lines 9-11 could probably be condensed into something like "This talk will share some takeaways that InboxDollars.com learned in scaling its PHP backend with RabbitMQ from X to Y [units]"
• In line 12, I'd say " ...questions you need to answer when scaling up your app" to reiterate the key point.

Thanks for including all the contextual metadata with your abstract!