CQRS and Event Sourcing with Prooph

Transcript

1. Presentation title CQRS + Event Sourcing Basic concepts explained with Prooph
2. Presentation title v 1. Why? 2. What is... 2.1 CQRS? 2.2 Event sourcing? 3. Prooph 3.1 Components 3.2 Code exploration Index
3. Presentation title WHY CQRS+ES? Disclaimer: My use and experienced benefits of CQRS and event sourcing may only apply to my context. Never use CQRS without guidance from someone who has real-world experience using it.
4. Presentation title Ben Adrian Sarmiento foodpanda engineering manager / full stack developer self-learned Bright (acquired), Cloud Sherpas (acquired), Carmudi (acquired)
5. Presentation title
6. Presentation title Why? Scalability Flexibility Structure Clear Rules Shifts complexity Why not? Not robust Boilerplate Complex, many layers
7. Presentation title CQRS
8. Presentation title Query Command Command Query Responsibility Segregation
9. Presentation title Read Write Command Query Responsibility Segregation
10. Presentation title Read Write Command Query Responsibility Segregation User
11. Presentation title Read Write Command Query Responsibility Segregation User ▪ getByID ▪ register
12. Presentation title Read + Write Command Query Responsibility Segregation User ▪ getByID ▪ register ▪ getAll ▪ deactivate ▪ delete ▪ promoteToRole Single model
13. Presentation title Read Write Command Query Responsibility Segregation Bank Account ▪ getAccountNumber ▪ getCurrentBalance ▪ getAllOneYearOldAccounts ▪ open ▪ deposit ▪ withdraw ▪ applyInterest
14. Presentation title Disclaimer: DO NOT APPLY CQRS ON YOUR WHOLE APPLICATION!
15. Presentation title
16. Presentation title ▪ You have a Document model stored in a MySQL server (RDBMS) ▪ Search feature launched, only need to search in Document.title and Document.content ▪ You survive by doing %needle% queries in MySQL ▪ PM asks for PDF support, content should be searchable ▪ Unstructured content but structured queries (translated titles, etc.) Document management app Single model evolved to a read/write model Document management app
17. Presentation title Scale either sides independently depending on load Teams can work in parallel Additional benefits
18. Presentation title Event Sourcing
19. Presentation title Event sourcing vs. CRUD
20. Presentation title ▪ I need all the items that are currently in the cart CRUD ▪ I need all items that were removed from the cart 5 mins before checkout Event sourcing Comparison (e-commerce app) Answers different questions, addresses different needs
21. Presentation title ▪ ItemWasAddedToCart ▪ UserCelebratedBirthday ▪ TodoWasMarkedAsDone Objects that goes through significant phases ▪ Project ◦ Assignments, deliveries ▪ JIRA ticket ▪ Caterpillar Examples Event Birthday, Graduation, Monthsary
22. Presentation title [show prooph https://github.com/prooph/proophessor-do]
23. Presentation title Thank You!!! -----