Why Message Driven?
0 likes133 views
The document discusses Richard McIntyre's background working in Japan for 15 years and now as a principal engineer. It then covers messaging patterns and message-driven architecture, describing how it allows for loose coupling, scalability, elasticity, and fault tolerance compared to traditional request/response systems. It concludes by discussing using a message broker like Kafka or RabbitMQ to enable auto-scaling and building a more cohesive platform and microservices using messages as the integration mechanism.
Why Message Driven?
- 1. RichardMcIntyre @mackstar Β· Lived in Japan for 15 years Β· η₯ζΈ Β· γγͺγΌγ©γ³γ΅γΌ Β· 2011εΉ΄γ«εΈ°ε½
- 2. Β· Principal Enginer Β· Full Stack Β· Tinkers with JS, Elixir & Java Β· BDD framework ShouldIT? Β· Headless CMS Spout
- 23. β26April1982
- 28. Disclaimer
- 41. Β· No Persistence Β· No Caching Β· Slow requests Β· Concurrency problems Β· Each client needs to know where each service is Β· Work needs to be done when endpoints change Β· When there are service/network issues no other services know about it
- 42. GraphQL Product Customer Basket Quote Content Campaigns Offers Rules Order Subsmission Line Check Engineer Visit Store Locations Propositions External Services Transitional Built.io OogwaySALLWS MCS Micro-services IdentityCBS FSP Afο¬liates OMv2 RangoPIMMRef Data PAS Classic Clean Micro Services MCS KANA Cache Session Ofο¬ine Message Queue Message Service Retentions Eligibility Consul Vault Prereg Rules Checkout Targeted Sales Prereg Mobile Misc Components Sky Pages Reports Portfolio
- 43. MessageQueues
- 44. ObserverPattern
- 48. MessagePatterns
- 50. Action Component Listener Component Message Message Sends Delivers Queue Listener Component Competing Consumers Pattern
- 51. Action Component Listener Component Message Sends Queue Listener Component Exchange Message Message Delivers Delivery to more components
- 52. Action Component Listener Component Errors Listener Component Exchange Routing Errors Debug Info
- 55. Amessageis:
- 56. Lightweight
- 57. Immutable
- 58. Categorised
- 59. Subscribe-able
- 60. Ignore-able
- 61. Distribute-able
- 64. Idempotent
- 65. Push(notpull)
- 72. Looslycoupled
- 73. Scale-able
- 74. Elastic
- 75. Reactive
- 76. Faulttolerant
- 77. AutoDiscover
- 88. Problems
- 90. Conclusion
- 92. SystemHealth
- 95. Features