Microservice communication with RabbitMQ

Talk from RubyMeditation#19 in Kyiv

Transcript

1. Ruby Meditation #19 Microservice communication with RabbitMQ Tetiana Chupryna
2. Disclaimer. Language
3. Татьяна Чуприна
4. Татьяна Чуприна Person of a million names
5. Тетяна Чуприна
6. Тетяна Чуприна
7. Tetiana Chupryna
8. Tetyana Chuprina
9. Tetjana Chuprina
10. Tetyiaana Chuprina
11. Tetiana Chupyra
12. Tetiana Chuprynas
14. Tania
15. Agenda ❖ Inter-service communication problematics ❖ JSON over HTTP option ❖ Message queues option ❖ RabbitMQ ❖ Integration with Ruby
16. –Steven McConnell, Code complete “Important developments often arise out of analogies. By comparing a topic you understand poorly to something similar you understand better, you can come up with insights that result in a better understanding of the less-familiar topic.” The importance of Metaphors
17. Luggage for dummies
18. Luggage for dummies
19. Luggage for dummies Drop-off
20. Luggage for dummies Drop-off Sorting
21. Luggage for dummies Drop-off Sorting
22. Luggage for dummies Drop-off Sorting Sorting
23. Luggage for dummies Drop-off Sorting c a r o u s e l Sorting
24. Luggage for dummies Drop-off Sorting c a r o u s e l Sorting
25. Game changer
27. Event-based system
28. Scalable
29. Maintainable
30. Back to clouds
31. Microservice communication ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
32. Inter-service communication ❖ New problem which doesn’t exist in monolith ❖ So many ways to success ❖ So many pitfalls
33. JSON over HTTP Re use API at least Basic Auth 100% control
34. JSON over HTTP
35. You can’t be 100% sure
37. Design failure to success
38. Sidekiq to the resque ❖ Handle “other side” failures gracefully ❖ Retry if needed
39. Procs ❖ Easy ❖ Quick ❖ Dirty ❖ Great choice for small apps
40. Cons ❖ Bad in scaling ❖ Pain for maintenance ❖ Net::HTTP
41. Inter-service communication
42. Break it. Make it. ❖ Decouple service interaction ❖ Keep messages in temporary storage (mailbox?) ❖ Make all asynchronous
43. Message queues ❖ Message-oriented middleware ❖ Applicable not only for web-applications ❖ Async communication protocol
44. Kafka JBossMessaging Oracle OpenMQ mail.ru Tarantool
45. RabbitMQ
46. Reasons to use ❖ Written in Erlang ❖ Fast&Reliable ❖ Easy to setup ❖ Client libraries on all major languages (Ruby yippee!) ❖ Advanced Message Queuing Protocol
47. In a nutshell
48. Direct exchange routing
49. Fanout exchange routing
50. Topic exchange
51. Queue properties ❖ Name ❖ Durable ❖ Exclusive ❖ Auto-delete ❖ Arguments
52. Bindings ❖ Direct: by routing_key ❖ Multiple bindings ❖ Mask routing
53. Security ❖ TLS (transport layer security) ❖ SSL ❖ authentication ❖ authorization
54. Setup Rabbit ❖ Install and run ❖ No painful dependancies
55. Bunny ❖ Ruby client for RabbitMQ ❖ Lightweight ❖ Up&go
56. Bunny usage
57. Sneakers ❖ Background processing framework for Ruby and RabbitMQ ❖ Can be used for high workload ❖ Up&go (as always)
58. Worker
59. Procs ❖ Scalable ❖ Maintainable ❖ Lightweight
60. Cons ❖ Need additional infrastructure eq(Money) ❖ Overkill for small projects ❖ Need additional knowledge
61. Afterwords ❖ Decoupling message flow from app changes app design and in general makes all easier. ❖ Decoupling message flow makes programs more safe and scalable. ❖ Message queues are a save choice for inter-service communication where RabbitMQ is a solid option. ❖ Ça dépend
62. Share your stories of inter-service communication
63. Massive thanks
64. Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks Thanks