The document discusses event-driven architecture (EDA). EDA is a software architecture pattern that promotes processing, detecting, consuming, and reacting to events. An event is defined as a significant change in state. EDA allows for real-time processing as events happen, push notifications, and immediate actions by consumers without waiting. EDA is scalable in processing, design, and adapting to change. It focuses on domain logic and collaborating with domain experts. EDA uses message brokers, producers that generate events, and consumers that process events.

1. EventDrivenArchitecture
Shadrach Jabonir

2. “Theonly
constantis
Change”
2

3. “Itisnotthe
Strongestofthe
speciesthatsurvives
buttheonemost
adaptabletochange”
3

4. Roadmap
Platform as a
Service
Containerized
Application
Event/Message
Driven
Architecture
Microservices

5. Event Driven
Architecture
Known as message-driven
architecture, is a software
architecture pattern promoting
to production, detection,
consumption of, and reaction of
events.
Event can be defined as a
significant change in state.
5
Definition

6. Event Driven Architecture
History
Type of
interaction
Initiator Participants
Time Driven Time
The Specified
System
Request Driven Client Client and Server
Event Driven Event Open-ended
6

7. Event Driven Architecture
History
• We want to transform our
system into real time
processing
• We want to give our
customer and business user
what they want and when
they want it
• SOA+EDA will enable a layer
of high value services
7

8. Event Driven Architecture
•Scalable in processing
•Scalable in design
•Scalable in change
8
Why

9. Event Driven Architecture
• Real Time event as they happen
on producer
• Push Notification
• One Way (Fire and Forget)
• Immediate action at the
consumer
• Informational, not command!
9
Concepts

10. Event Driven Architecture
• Domain  A sphere of
knowledge or activity around
which the application logic
revolves
• Domain Driven Design is the
expansion upon and application
of domain concept, as it implies
to the development of software
• Eric Evans
10
Domain Driven Design

11. Event Driven Architecture
• Focus on domain and domain
logic
• Base complex on the models of
the domain
• Constantly collaborate with
domain experts in order to
improve the application model
and resolve any emerging
domain related issues
11
Domain Driven Design

12. Event Driven Architecture
Order
Event
Calculate
Processor
Inventory
Processor
Payment
Processor
Trade
Processor
Logging
Processor
Report
Processor
12
Way of thinking

13. Event Driven Architecture
Aggregate
Service
Calculate
Processor
Inventory
Processor
Payment
Processor
Trade
Processor
13
Way of thinking

14. Event Driven Architecture
Benefit
• Support business better
with no batch or waiting
• No point to point
integration (fire and forget)
• Enable high performance
through high scalability
14

15. Architecture
Message
Broker
Producer
Producer
Consumer
Consumer
Consumer
Consumer
Consumer
Producer
15
Event Driven Architecture

16. References
• https://www.slideshare.net/stnor/event-driven-
architecture-3395407?qid=ca42f1a4-2f36-4e51-
ba6c-7d42dc49a353&v=&b=&from_search=2
• https://www.slideshare.net/Pivotal/eventdriven-
architecture-traps-115609034?qid=5722aac1-
ac2f-4a61-921e-
8c33d93b4b83&v=&b=&from_search=3
• https://www.slideshare.net/igrigorik/event-driven-
architecture-meshu-ilya-grigorik?qid=7b33421d-
86ca-4f4f-b967-
449284794892&v=&b=&from_search=4
• https://www.slideshare.net/brianritchie1/building-
eventdriven-systems-with-apache-
kafka?qid=d354a2cc-a146-4b84-a76e-
bd75a62f9c3b&v=&b=&from_search=10
16

17. 17
We enhance our system to improve ourselves and help our friends

18. ThankYou
Shadrach Jabonir
+628118032213
shadrachjabonir@gmail.com
https://github.com/shadrachjabonir