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.

2. COMMUNICATING

3. IS

4. HARD!

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

6. Once upon a time…

9. <CFQUERY>
<CFMAIL>
<CFFORM>
<CFLOOP>
<CFARGUMENT>
<CFWTF>

10. … happily ever after?

13. SOA
“After analysing both languages I came to the
conclusion a migration is almost like copy & paste”

14. SOA
both Java & C# languages
almost like copy & paste

15. Java != .NET

17. SOA
SOA

19. SOA
SOA
Microservices

21. Communication

22. Queues

23. Why queue?
Everybody hates queues!
Except for the British
Why queue?

24. 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”
What?

25. 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”
What?

26. Back into how communications
work

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

28. Email.SendMessage(msg)

29. Pub/Sub
Publisher
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

30. Happy days…

31. But that’s not all you get

32. Traffic Shaping
High traffic == GOOD!

33. Scalability
Apps should scale
Scalability

34. IsolationIsolation
Keep your errors away

35. Cross platformCross Platform
Best tool for the job

37. Why !queue?I got it wrong

38. Payments
Processed payments
Payments

39. Feedback
Made my users wait
Feedback

40. What now?What now?

41. Demo time

42. Key takeaways
✓ Communicating is hard!
✓ High traffic is a good problem
to have
✓ Think at scale
✓ Stay away from exceptions
✓ Use the best tool for the job
✓ Queues aren’t the answer to
everything
Key takeaways

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

44. WE’RE HIRING!
We’re hiring for positions across our global office locations:
We’re looking for people that work hard, think smart, and move fast to join us on the following
teams:
• Customer Support
• Engineering
• Finance & Admin
• Marketing
• Product
• Sales
FIND OUT MORE AT bit.ly/twiliojobs OR SHOOT US
AN EMAIL AT jobs@twilio.com