Architecting the future

Transcript

1. © 2021, Amazon Web Services, Inc. or its Affiliates. Abid Jamil Engineering Manager - Dubicars Architecting the Future Unveiling the Power of Event-Driven Architecture
2. About Me • Open Source Contributor , CS Researcher • Active Tech Speaker • Community Builder
3. Agenda • Challenges with distributed systems • Journey to event-driven architectures • Event Storming
4. © 2021, Amazon Web Services, Inc. or its Affiliates. Challenges with Distributed Systems
5. Micro services start simple 201 201 😀
6. Synchronous API challenges over time Producer Consumers 😩
7. Event-driven architectures drive reliability and scalability Asynchronous Events Improve responsiveness and reduce dependencies Event Routers Abstract producers and consumers from each other Event Stores Buffer messages until services are available to process
8. Reliable, resilient, and independently scalable “If your application is cloud-native, or large-scale, or distributed, and doesn’t include a messaging or event component, that’s probably a bug.” Tim Bray General-purpose Internet-software geek 😀
9. © 2021, Amazon Web Services, Inc. or its Affiliates. Journey to Event-Driven Architectures
10. Journey to event-driven architectures STEP 1 Start with the domain
11. event [i-’vent] noun A signal that a system’s state has changed.
12. © 2021, Amazon Web Services, Inc. or its Affiliates. Event-driven modeling
13. © 2021, Amazon Web Services, Inc. or its Affiliates. Event-driven architectures start with business events
14. Map events to business domains using attributes, not entities Retail Fulfillment Support
15. Events are observable, not directed Directed commands Observable events
16. Choreograph events between domains using subscriptions Retail Fulfillment OrderCreated Notification Notify me when an order is created Subscription
17. Journey to event-driven architectures STEP 2 Pick an event router
18. Why do you need a router?
19. Why do you need a router?
20. Why do you need a router?
21. Why do you need a router?
22. Why do you need a router?
23. © 2021, Amazon Web Services, Inc. or its Affiliates. Event Storming
24. © 2021, Amazon Web Services, Inc. or its Affiliates. Events ( Orange ) These are the most important and widely used component in Event Storming and represent the domain events and anything that is relevant to a domain expert. They are written in past tense and provide the underlying details that feed into the later categorization steps.
25. © 2021, Amazon Web Services, Inc. or its Affiliates. Commands ( blue ) These are requests to do something. They can originate from a user or system or by another event.
26. © 2021, Amazon Web Services, Inc. or its Affiliates. System ( Pink ) These represent systems involved in the domain. They may issue commands or receive commands along with triggering events.
27. © 2021, Amazon Web Services, Inc. or its Affiliates. Actor ( Yellow ) These are human users involved in the process. They may be a single person or a department/team. Yellow sticky notes help show how complicated the workflow of a business process can be based on the number of departments involved and the amount of back and forth.
28. © 2021, Amazon Web Services, Inc. or its Affiliates. Aggregate ( tan ) This is the first level of categorization and can be thought of as the “thing” that a group of events operate on. Typically they’re a noun and can be identified when there’s a cluster of events dependent on one another.
29. © 2021, Amazon Web Services, Inc. or its Affiliates. Policy ( grey ) These represent standards or rules that may need to be executed, such as rules for a compliance policy.
30. Why do you need a router?
31. Why do you need a router?
32. Why do you need a router?
33. Why do you need a router?
34. Why do you need a router?
35. Why do you need a router?