7 Reasons why your microservices should use Event Sourcing & CQRS
•
1 like•542 views
A look at some of the advantages provided with microservices that use event sourcing and command query responsibility segregation (CQRS).
Recommended
Recommended
More Related Content
Similar to 7 Reasons why your microservices should use Event Sourcing & CQRS
Similar to 7 Reasons why your microservices should use Event Sourcing & CQRS (20)
More from Hugh McKee
More from Hugh McKee (15)
Recently uploaded
Recently uploaded (20)
7 Reasons why your microservices should use Event Sourcing & CQRS
- 1. 7 Reasons why your microservices should use Event Sourcing & CQRS Hugh McKee (@mckeeh3), Developer Advocate
- 2. 7 Reasons why your microservices should use Event Sourcing & CQRS Hugh McKee (@mckeeh3), Developer Advocate
- 3. Large and Complex Systems
- 4. Large and Complex Systems
- 5. Large and Complex Systems Processing
- 6. Large and Complex Systems Processing Persistence
- 7. CQRS - Command Query Responsibility SegregationCQRS - Command Query Responsibility Segregation
- 8. CQRS - Command Query Responsibility Segregation System of loosely coupled services 1. Independently deployable 2. Owns its schema 3. API only access to data
- 9. CQRS - Command Query Responsibility Segregation System of loosely coupled services 1. Independently deployable 2. Owns its schema 3. API only access to data
- 10. CQRS - Command Query Responsibility Segregation System of loosely coupled services 1. Independently deployable 2. Owns its schema 3. API only access to data
- 11. CQRS - Command Query Responsibility Segregation System of loosely coupled services 1. Independently deployable 2. Owns its schema 3. API only access to data
- 12. CQRS - Command Query Responsibility Segregation
- 13. CQRS - Command Query Responsibility Segregation Are you crazy?
- 14. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS
- 15. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 0Reason
- 17. 1
- 18. 1 2
- 19. 1 2 3
- 20. 1 2 3 4
- 21. 1
- 22. 1 2
- 23. 1 2 3
- 27. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 1Reason
- 28. Smooth transition from DDD & Event Storming to implementation
- 29. Domain Driven Design Event Storming Smooth transition from DDD & Event Storming to implementation
- 30. Commands & Events Microservices Domain Driven Design Event Storming Smooth transition from DDD & Event Storming to implementation
- 31. Commands & Events Microservices Domain Driven Design Event Storming Event Sourcing & CQRS Smooth transition from DDD & Event Storming to implementation
- 32. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 2Reason
- 54. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 3Reason
- 55. Break the read versus write performance bottleneck Optimize Reads? Writes
- 56. Optimize Writes? Break the read versus write performance bottleneck Reads
- 57. Break the read versus write performance bottleneck
- 58. Break the read versus write performance bottleneck
- 59. Break the read versus write performance bottleneck
- 60. Break the read versus write performance bottleneck
- 61. Break the read versus write performance bottleneck
- 62. Break the read versus write performance bottleneck Eventually consistent
- 63. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 4Reason
- 64. Elevate the concurrency barrier
- 65. Elevate the concurrency barrier
- 66. Elevate the concurrency barrier
- 67. Elevate the concurrency barrier
- 68. Elevate the concurrency barrier
- 69. Elevate the concurrency barrier
- 70. Elevate the concurrency barrier
- 71. Elevate the concurrency barrier
- 72. Elevate the concurrency barrier
- 73. Elevate the concurrency barrier Eventually consistent
- 74. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 5Reason
- 75. • at-most-once • at-least-once • exactly-once Semantics of delivery (maybe-once) (once-or-more) (essentially-once) Simplify and harden messaging
- 76. Simplify and harden messaging At-least-once Push
- 77. Simplify and harden messaging At-most-once Push
- 78. Simplify and harden messaging At-least-once Pull
- 79. Simplify and harden messaging At-least-once Pull
- 80. Simplify and harden messaging At-least-once Pull
- 81. 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery 7 Reasons why your microservices should use ES & CQRS 6Reason
- 90. 7 Reasons why your microservices should use ES & CQRS 7 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery Reason
- 91. Graduate from the IT Nursery Reduce Governance Reduce Ceremony and Ritual Increase Velocity
- 92. Graduate from the IT Nursery Reduce Governance Reduce Ceremony and Ritual Increase Velocity
- 93. Graduate from the IT Nursery Reduce Governance Reduce Ceremony and Ritual Increase Velocity Organized Chaos
- 94. Graduate from the IT Nursery Reduce Governance Reduce Ceremony and Ritual Increase Velocity Organized Revolution
- 95. Graduate from the IT Nursery Reduce Governance Reduce Ceremony and Ritual Increase Velocity People are very open-minded about new things - as long as they're exactly like the old ones. -Charles F. Kettering
- 96. 7 Reasons why your microservices should use ES & CQRS 0. What is Event Sourcing & CQRS 1. Smooth transition from DDD & Event Storming to implementation 2. Reduce service coupling 3. Break the read versus write performance bottleneck 4. Elevate the concurrency barrier 5. Simplify and harden messaging 6. Eliminate service coupling 7. Graduate from the IT Nursery
- 97. Hugh McKee (@mckeeh3), Developer Advocate