2nd attempt at this talk idea

talk_submission.md

How RabbitMQ Saved My (S)aSS

What happens to your web app when a databases update fails? Or the email service is unreachable due to network hiccups? Will the front-end survive bad code crashing the back-end? Admit it - the web app will crash and show a useless "server error" message. But there is hope! Messaging servers, like RabbitMQ, work wonders in the face of failure - decoupling processes and allowing for re-try when things come back up.

In this talk, I'll show you how I re-architected SignalLeaf to deal with crashes and sometimes-connected services. You'll hear tales from the trenches of success and failure with RabbitMQ and Node.js. You'll see how a message queue can help you build a more resilliant web app. And you'll clean up your code at the same time! Rejoice as your application architecture improves by leaps and bounds, with RabbitMQ!

ok, i'm working on the title a bit... going for something a bit cheeky but still more along the lines of what rob suggested.

also swtiched the first paragraph around like jakefolio suggested

not sure i can go for a full story like you're suggesting, rob. that's a bit long for an abstract, but it's a great story that i will probably use elsewhere :)

MUCH better!

1. remove ", like this".
2. s/sucess/success

:)

Love the title - very good :). Don't like the first paragraph - it's argumentative and can be a bit offhandedly accusatory. What happens if...? is such a firecracker of a sentence; it's the "you can't prove a negative" kind of thing.

I really think you should stay positive; I like this abstract but...

What happens to your web app when a databases update fails? Or the email service is unreachable due to network hiccups? Will the front-end survive bad code crashing the back-end?

With this sentence I'm already formulating my response to you: I'm not an idiot, this isn't my first app. I can handle write failure as well as email not working. Yes, I've got it covered.... You're challenging your audience into a defensive posture - this is offensive by definition.

Admit it - the web app will crash and show a useless "server error" message. But there is hope!

I really don't like that you're assuming that I don't know what I'm doing :). Let's be more positive! Tell me in the first sentence your epiphany!

Last year I saved my business by using message queues. I was quite surprised, and it changed the way I do everything. Maybe it can help you too.

Not offensive - truthful! Hmmmmm maybe I can learn something from this guy who launched a business using message queues... - that's what I would be thinking. Rather than maybe I'll skip this talk from some guy who thinks everyone else is doing it wrong.