Event driven design (part 2)/ patterns/ event patterns By Nima Shokouhfar
This mindmap provides an overview of key messaging patterns used in distributed systems for communication between applications. It highlights different patterns such as Point-to-Point Messaging, Publish/Subscribe, Request-Response, and Fire-and-Forget, along with their use cases, pros, and cons. Patterns like Priority Queue, Work Queue, and Dead Letter Queue are also explained for handling specific workloads, prioritization, and error handling. The mindmap emphasizes how messaging patterns im...
1. others
1.1. styles
1.1.1. bad
1.1.2. good
1.1.3. not as good
1.1.4. not as bad
1.1.5. important
1.1.6. warning
1.1.7. link
1.2. AUTHOR
1.2.1. Nima Shokouhfar
1.2.1.1. Linkedin
1.2.1.1.1. Follow me on LinkedIn to stay updated on my latest professional insights and tech projects!
1.2.1.2. Youtube
1.2.1.2.1. code with nima
1.2.1.2.2. ideariver
1.2.1.3. Medium
1.2.1.3.1. ✍️ Follow me on Medium to read my latest articles on tech, coding, and innovation!
1.2.1.4. Github
1.2.1.4.1. ⭐️ Give my projects a star on GitHub and explore my repositories to discover new tools and innovations!
1.2.1.4.2. 💖 Sponsor me on GitHub to support my open-source contributions and help me create even more useful projects!
1.2.1.5. upwork
1.2.1.5.1. 💼 Hire me on Upwork for freelance projects. Let’s work together to bring your tech ideas to life!
1.2.1.6. main website: ideariver.ca
1.2.1.6.1. 🚀 Visit IdeaRiver.ca for all my latest projects, blogs, and ways to connect!
2. main
2.1. Messaging patterns
2.1.1. good one
2.1.1.1. Key Messaging Patterns and Use Cases:
2.1.1.1.1. - **Putting and Getting Messages:**
2.1.1.1.2. - **Point-to-Point Messaging:**
2.1.1.1.3. - **Publish/Subscribe (Pub/Sub):**
2.1.1.1.4. - **Request-Response Messaging:**
2.1.1.1.5. - **Message Expiry:**
2.1.1.2. Why Use Messaging Patterns:
2.1.1.2.1. - Messaging systems decouple applications, meaning they don’t need to be online and responsive at all times.
2.1.1.2.2. - It’s essential to choose the right messaging pattern for your use case, and sometimes multiple patterns are needed for different scenarios.
2.1.2. patterns
2.1.2.1. 10. Request-Response with RabbitMQ (Reply-To Queue)
2.1.2.1.1. Description:
2.1.2.1.2. Use Cases:
2.1.2.1.3. pro/cons
2.1.2.1.4. request-response pattern (Reply-To Queue)
2.1.2.2. 1. Fire-and-Forget Pattern
2.1.2.2.1. Description:
2.1.2.2.2. Use Cases:
2.1.2.2.3. pro/cons
2.1.2.3. 2. Publish-Subscribe Pattern
2.1.2.3.1. Description:
2.1.2.3.2. Use Cases:
2.1.2.3.3. pro/cons
2.1.2.4. 3. Work Queue (Task Queue) Pattern
2.1.2.4.1. Description:
2.1.2.4.2. Use Cases:
2.1.2.4.3. pro/cons
2.1.2.5. 4. Dead Letter Queue (DLQ) Pattern
2.1.2.5.1. Description:
2.1.2.5.2. Use Cases:
2.1.2.5.3. pro/cons
2.1.2.6. 5. Topic-Based Routing Pattern
2.1.2.6.1. Description:
2.1.2.6.2. Use Cases:
2.1.2.6.3. pro/cons
2.1.2.7. 6. Priority Queue Pattern
2.1.2.7.1. Description:
2.1.2.7.2. Use Cases:
2.1.2.7.3. pro/cons
2.1.2.8. 7. Competing Consumers Pattern
2.1.2.8.1. Description:
2.1.2.8.2. Use Cases:
2.1.2.8.3. pro/cons
2.1.2.9. 8. Routing Key (Direct Exchange) Pattern
2.1.2.9.1. Description:
2.1.2.9.2. Use Cases:
2.1.2.9.3. pro/cons
2.1.2.10. 9. Delayed Messaging Pattern
2.1.2.10.1. Description:
2.1.2.10.2. Use Cases:
2.1.2.10.3. pro/cons
2.1.2.11. 11. Aggregator (Gather and Combine Messages)
2.1.2.11.1. Description:
2.1.2.11.2. Use Cases:
2.1.2.11.3. pro/cons