Quentin Adam from Clever Cloud gave a presentation on using RabbitMQ for message brokering in microservices applications. RabbitMQ allows services to communicate asynchronously through exchanges, queues and bindings. It supports common messaging patterns like pub/sub and request/response. Clever Cloud uses RabbitMQ for real-time application logging and log draining to external services. RabbitMQ is battle tested, supports many languages, and Clever Cloud offers it as a fully managed service.

1. RABBITMQ 101 :
JOB SCHEDULING,
MICROSERVICES
COMMUNICATION, EVENT-
BASED DATA STREAM…
HOW TO COOK THE
RABBIT?
QUENTIN ADAM
@WAXZCE
CLEVER CLOUD

2. Quentin ADAM from the Clever Cloud
@waxzce on twitter – github- soundcloud – instagram ….
WHO AM I ?

3. MY DAY TO DAY WORK :
CLEVER CLOUD,
THE IT AUTOMATION COMPANY

4. KEEP YOUR APPS ONLINE. MADE WITH
NODE.JS, SCALA, JAVA, RUBY, PHP,
PYTHON, GO…

5. AND LEARN A LOT OF THINGS ABOUT
YOUR CODE, APPS, AND GOOD/BAD
DESIGN…

6. GIVE BACK TO THE COMMUNITY
NEVER
GONNA
LET YOU
DOWN
clever-cloud.com

7. APPLICATIONS

8. MORE AND MORE COMPLEX

9. SPLIT APPLICATIONS?

10. FOCUS ON SPECIFIC STACK FOR
SPECIFIC USE?

11. COMMON CASE: PHP SITE WITH
WEBSOCKETS, GO TO NODE?

12. APPLICATIONS NEEDS TO
COMMUNICATES

13. WEB DEV FIRST THINK : HTTP

14. UNIDIRECTIONAL

15. NO ACK

16. ROUTING

17. AUTH

18. WHAT DO WE
NEED TO
SHARE WITH
OTHERS
SERVICES?

19. EVENTS

20. DIFFUSE
EVENTS TO ALL
SERVICES
COMPONENTS
WHERE IT’S
NEED

21. MESSAGE BROKER

22. MESSAGE BROKER
• JMS
• 0MQ
• Redis
• Celery
• Kafka
• Files + Cron
• rabbitMQ

23. ADVANCED
MESSAGE
QUEUING
PROTOCOL
PROTOCOL

24. Originally made by JP Morgan Bank (USA)
AMQP

25. Now OASIS section
AMQP

26. Many implementations
AMQP

27. RABBITMQ

28. Is the well known implementation & made with erlang
RABBIT MQ

29. ERLANG OTP

30. Speak almost all languages and platform
RABBIT MQ

31. FEW
CONCEPTS

32. Think as cluster name for sharing cluster nodes for multiples purpose
VIRTUAL HOST

33. Client pushing messages
PUBLISHER

34. Client getting messages
CONSUMER

35. Yeah, basically tcp + auth
CONNECTIONS

36. “logical connection”
CHANNELS

37. See this as INBOX
EXCHANGES

38. See this as WAY OUT
QUEUES

39. And use a routing key
YOU HAVE TO EXPLICITLY BIND A
QUEUE ON AN EXCHANGE

40. It’s an event, what we need to share
MESSAGES

41. HEADERS / BODY
Headers
• context
• "Routing Key"
Body
• Payload
• binary

42. WRAP UP

43. THE DIFFERENT EXCHANGES

44. Perfect repartition with load balancing & routing key
AMQP.DIRECT

45. Tell all messages to Anyone suscribe
AMQP.FANOUT

46. Basically a FANOUT using routing key
AMQP.TOPIC

47. Direct exchange using matching on Headers
AMQP.MATCH

48. LISTENING ONE QUEUE USING MANY
CONSUMERS

49. YOU CAN NOW
DESCRIBE
YOUR
TOPOLOGY

50. ACK

51. NO-ACK DOWNSIDE

52. MESSAGING LIFECYCLE

53. BUFFER BY CONSUMER

54. Durable & exclusive
QUEUE PARAMS

55. QUEUE LIFE CYCLE

56. Disk or RAM debate
LOTS OF MESSAGES IN MEMORY?

57. REQUEST/REPLY PATTERN

58. ENJOY
TOPOLOGY CRASH TEST

59. EXAMPLE:
CLEVER CLOUD REAL TIME LOG
Exchange
FanOut
Logs
Routing key
= app id
Logs from
logstash, 1
message
per line
1 queue by WS, RK = appID,
name = appid + autogen
1 queue by WS, RK = appID,
name = appid + autogen
1 queue by WS, RK = appID,
name = appid + autogen

60. CLUSTER WAY OF LIFE

61. QUEUE HA

62. FEDERATION

63. PLUGINS

64. STOMP, MQTT, WEBSOCKETS

65. More than 5 years production history
IS IT BATTLE TESTED ?

66. WHY IT’S
SO COOL

67. I CAN BRANCH WHERE I WANT

68. EXAMPLE
EVOLUTION OF USAGES

69. EXAMPLE:
CLEVER CLOUD REAL TIME LOG
+ LOGS DRAIN
Exchange
FanOut
Logs
Routing key
= app id
Logs from
logstash, 1
message
per line
1 queue by WS, RK = appID,
name = appid + autogen
1 queue by WS, RK = appID,
name = appid + autogen
1 queue by WS, RK = appID,
name = appid + autogen
1 durable queue by drain,
using RK=appID & name =
drain_<appID>_<drainID>
1 durable queue by drain,
using RK=appID & name =
drain_<appID>_<drainID>
1 durable queue by drain,
using RK=appID & name =
drain_<appID>_<drainID>
1 durable queue by drain,
using RK=appID & name =
drain_<appID>_<drainID>

70. RUN IT WITH PHP
Send
• plain access, like
webservice or DB
Receive
• Worker with PHP
launch using CLI
• please use systemd
and not tmux open
shell :-D
https://github.com/php-amqplib/php-amqplib

73. SOON OPEN SOURCE, NEW ACL ADD-ON
+ PRE-SIGNED AUTH

74. Soon a regular add-on, just ask support to get beta access
YOU CAN TEST IT ON CLEVER CLOUD ;-)

75. Give CLEVER-CLOUD.COM a try 
I’m @waxzce on twitter
THX FOR LISTENING
Clever Cloud gift coupon:
phptour16