How many times did you have to get two different API’s to communicate with each other and were left wondering what was the best way to get them talking? XML? JSON? HTTP? Sound familiar? You have used service oriented architecture but your projects turned out “speaking different languages” and you’re now faced with the arduous task of being the translator. Life’s too short and #yolo! Although you may have opted for the most appropriate technology, the correct design pattern and the optimal algorithms, if you don’t get your applications talking correctly they will be as good as a plate of spaghetti. In this presentation I’ll show you the secret many companies have been using for years to be able scale and respond to requests faster. I will tell you about some of the things you should look for when choosing your messaging system, and what are the things to look for when you start developing your messaging system.

1. Just Queue it!
<Say>Hello Barcelona!</Say>
@marcos_placona
marcos@twilio.com
Developer Evangelist @ Twilio

2. Why queue?
Everybody hates queues!
Except for the British
And the Germans

3. What!?
“An enterprise messaging system is a set of standards that allows
organisations to send semantically precise messages between
computer systems. They promote loosely coupled architectures
that allow changes in the formats of messages to have minimum
impact on subscribers”

4. Meow!
Woof!
Oh Hai!
Email.SendMessage(msg)

6. Email.SendMessage(msg)

7. Traffic Shaping
High traffic == GOOD!

8. Scalability
Apps should scale
Scalability

9. IsolationIsolation
Keep your errors away

10. Cross platformCross Platform
Best tool for the job

11. How it works
Producer
I want to send an
email
I’m uploading an
image
Update my
currency
conversions
Got any emails for
me? $$$
I am The
Doctor!
Mrs. Banker
Messaging Bus
Mr. Postman
The Doctor

12. Why !queue?

13. Payments
Don’t break the flow

14. Feedback
Don’t leave me hanging

15. What now?

16. Key takeaways
✓ Communication is hard!
✓ High traffic == GOOD
✓ Scale, scale, scale…
✓ Stay away from exceptions
✓ Coding should be fun
✓ Queues aren’t for everyone

17. @marcos_placona
marcos@twilio.com
Developer Evangelist @ Twilio
Questions?