R-Messe – Sockets and Event Architecture
0 likes273 views
The document discusses the use of sockets and event-driven architecture in Rakuten's R-Messe communication tool. Sockets allow for instant, bidirectional messaging between merchants and customers, improving the user experience. This is compared to traditional HTTP requests which require multiple exchanges. Examples show how sockets reduce the number of messages needed and how events can be received and processed in real-time. The document advocates using the fastest tools available to simplify development and enhance user experiences.
R-Messe – Sockets and Event Architecture
- 1. Nov 9, 2019 Fukumoto Yoshiaki EC Business Dept. Rakuten, Inc.
- 2. 2 Who am I? Fukumoto Marcelo Yoshiaki – 29 years old Rakuten Application Engineer Brazilian Japanese descendant – Nikkei Third Generation – Sansei Working at Rakuten since January 2019.
- 3. 3 Sockets and Event Driven Architecture the power behind R-Messe • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools for giving the best User Experience
- 4. 4 Sockets and Event Driven Architecture the power behind R-Messe • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools for giving the best User Experience
- 5. 5 What is R-Messe? It is a communication tool created to control the inquiries between merchant and shopper. The idea is to have the best User Experience with the best technology we can offer.
- 6. 6
- 7. 7 • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools for giving the best User Experience
- 8. 8 What is Event Driven Archictecture? “The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events. ” Richards, M (oreilly.com, 2015)
- 9. 9 Change Color Event Message: “changeColor” Message data: { “color” : red” } Background color WHITE Background color RED
- 10. 10 Now it is red!
- 11. 11 Pros • The overall agility is higher. The response is quicker to changes of environment. • It is easy to deploy since it is naturally decoupled. • Performance is better, since it has the ability to execute many functions decoupled. But it is always related to how it is architectured and developed. • Scalability is natural too, since the listeners and really decoupled and independent. Cons • It is more difficult to test. There is many more tools for layered architecture to test, and you will need a prepared environment to test this. • It is more difficult to develop. It is a lot more complicated since there will be more message exchange and error handling conditions.
- 12. 12 Front side was always event driven Front side using all the listeners from the browser was always event based: • focus • blur • keydown/keypress • keyup • click • mouseover • dblclick • select • drag • submit
- 13. 13 • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools for giving the best User Experience
- 15. 15 No socket structure (HTTP Request) Request
- 16. 16 No socket structure (HTTP Request) Request Response
- 17. 17 What to do if you want an exchange of message for example? Using HTTP. Ask for new message
- 18. 18 What to do if you want an exchange of message for example? Using HTTP. Ask for new message Gives new message
- 19. 19 What to do if you want an exchange of message for example? Using HTTP. Ask for new message Gives new message Ask for new message
- 20. 20 What to do if you want an exchange of message for example? Using HTTP. Ask for new message Gives new message Ask for new message Respond that there is no more message
- 21. 21 What to do if you want an exchange of message for example? Using HTTP. Ask for new message Gives new message Ask for new message Respond that there is no more message Ask for new message
- 22. 22 What to do if you want an exchange of message for example? Using HTTP. Ask for new message Gives new message Ask for new message Respond that there is no more message Ask for new message Gives new message
- 23. 23 Using Socket reduces the exchange of messages and the exchange is stateless. Connect
- 24. 24 Using Socket reduces the exchange of messages and the exchange is stateless. Connect Gives new message
- 25. 25 Using Socket reduces the exchange of messages and the exchange is stateless. Connect Gives new message Gives new message
- 26. 26 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? SAD STATUS Employee Boss
- 27. 27 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? No SAD STATUS Employee Boss
- 28. 28 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? No Boss, is my salary increased? SAD STATUS Employee Boss
- 29. 29 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? No Boss, is my salary increased? No SAD STATUS Employee Boss
- 30. 30 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? No Boss, is my salary increased? No Boss, is my salary increased? SAD STATUS Employee Boss
- 31. 31 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? No Boss, is my salary increased? No Boss, is my salary increased? Yes Employee Boss SAD STATUS
- 32. 32 Let’s use a real life example of asking for salary increase. Http requests. Boss, is my salary increased? No Boss, is my salary increased? No Boss, is my salary increased? Yes HAPPY STATUS Employee Boss
- 33. 33 It does not need to ask all the time for a salary increase Connect SAD STATUS Employee Boss
- 34. 34 It does not need to ask all the time for a salary increase Connect Your salary increased Employee Boss SAD STATUS
- 35. 35 It does not need to ask all the time for a salary increase Connect Your salary increased HAPPY STATUS Employee Boss
- 36. 36 Or the salary increase can even come from another source Connect Your salary increased HAPPY STATUS CEO Employee Boss
- 37. 37 Let’s use another example on a train station, that consider how timing is important The train arrived? SAD STATUS
- 38. 38 Let’s use another example on a train station, that consider how timing is important The train arrived? No SAD STATUS
- 39. 39 Let’s use another example on a train station, that consider how timing is important The train arrived? No 1 minute SAD STATUS
- 40. 40 Let’s use another example on a train station, that consider how timing is important The train arrived? No The train arrived? 1 minute SAD STATUS
- 41. 41 Let’s use another example on a train station, that consider how timing is important The train arrived? No The train arrived? No 1 minute SAD STATUS
- 42. 42 Let’s use another example on a train station, that consider how timing is important The train arrived? No The train arrived? No 1 minute 1 minute SAD STATUS
- 43. 43 Let’s use another example on a train station, that consider how timing is important The train arrived? No The train arrived? No The train arrived? 1 minute 1 minute SAD STATUS
- 44. 44 Let’s use another example on a train station, that consider how timing is important The train arrived? No The train arrived? No The train arrived? Yes, but already departed 1 minute 1 minute SAD STATUS
- 45. 45 With sockets and event based architecture, you will receive the message at the right time Waiting for train SAD STATUS
- 46. 46 With sockets and event based architecture, you will receive the message at the right time Waiting for train Arrived SAD STATUS
- 47. 47 With sockets and event based architecture, you will receive the message at the right time Waiting for train Arrived HAPPY STATUS
- 48. 48 • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools for giving the best User Experience
- 49. 49 If we think about a merchant looking at R-Messe, you can see the message too late. So the fastest it shows on your screen is better.
- 50. 50 Our notion of speed is different now:
- 51. 51 Our notion of speed is different now: weeks
- 52. 52 Our notion of speed is different now: weeks instant
- 53. 53 The sockets are normally for instant messaging for an instant and faster interaction. But since it is faster, why can’t we use in everything? Maybe we can.
- 54. 54 • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools to improve User Experience
- 55. 55 Let’s show some code!
- 56. 56 • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools to improve User Experience
- 57. 57 If we think how to go to Sendai from Tokyo by Bus: 5h 47min
- 58. 58 If we think how to go to Sendai from Tokyo by Shinkansen: 1h 56min
- 59. 59 • R-Messe • Event Driven Architecture • Sockets • Instant Delivery • Code • Notion of speed • Tools to improve User Experience
- 60. 60 What I want to show is not about sockets or event driven architecture. The idea is how different tools can simplify our way of thinking or even improving our possibilities. Let’s always improve, always advance.
- 61. 61 What I want to show is not about sockets or event driven architecture. The idea is how different tools can simplify our way of thinking or even improving our possibilities. Let’s always improve, always advance. Any questions?