This a short presentation of the Event Architecture Concept applying to Mulesoft. The sample will be released on Github soon.

1. 12th August - Event Architecture
[SÃO PAULO]

2. All contents © MuleSoft Inc.
Agenda
2
• Introductions
• Event Architecture - What is next?
– Event Notification
– Event-Carried State Transfer
– Event Sourcing
• Event Architecture and Mule
• Sample
• Q&A

3. All contents © MuleSoft Inc.
Introductions
3
• Victor Felipe
• Integration Engineer at Avenue Code
• 5 years of experience about System’s
Integration
• Background: Oracle Fusion Middleware &
Mulesoft.

4. What’s Next?
Event Architecture

5. All contents © MuleSoft Inc.
Event Architecture
• Key Reasons to talk about:
– Alta presença de grandes Players no cenário de integração, em especial a Oracle.
– Alto acoplamento a Padrões de integração específicos.
– Avanço das discussões sobre Microservices.

6. All contents © MuleSoft Inc.
Event Architecture
• What is Event Architecture:
– Event Architecture (EDA) é uma abordagem arquitetural onde aplicações são
interpretadas como sistemas que reagem a EVENTOS.
“This style of thinking concentrates on looking at a system's interaction with its world as
transmissions of events. Inputs understood by forming an event list that describes each possible
input to the system tied to an event in the outside world. Similarly the system announces any
significant changes to itself by signaling events to outside systems.”
(Fowler, Martin - Focusing on Events 25 January 2006)

7. All contents © MuleSoft Inc.
Event Notification
7
Telecom Environment
Customers
Customer
Management
changeAddres()
event:ChangeAddres
publish
Loyalty Program
Billing System
Resource System
Low level of coupling What the hell is going on?

8. All contents © MuleSoft Inc.
Event-Carried State Transfer
Telecom Environment
Customers
Customer
Management
changeAddres()
event:ChangeAddres
publish
High availability and Resilience Lake of duplicated data
Billing System
customerscustomers

9. All contents © MuleSoft Inc.
Event-Sourcing
9
Audit and Replay Capability Replay Capability
Telecom Environment
Customer
Management
Event Store
event
Address Changed
Billing System
Others Systems
changeAddres()

10. Event Architecture & Mule

11. All contents © MuleSoft Inc.
Event Architecture & Mule
11
• Mulesoft Connectors:
– Mulesoft oferece uma vasta variedade de Conectores que o tornam uma ferramenta
flexível e robusta o suficiente para trabalhar orientada a Padrões de Integração.

12. Sample

13. All contents © MuleSoft Inc.
Sample Implementation
13
Experience APIs
salesOrder
Process APIs
System APIs
topic:customer.order creditScore
creditLine
shipping
Credit System
topic:order.failed
HTTP:POST
EventSourcing

14. All contents © MuleSoft Inc.
Source
14
• Sources:
– Event-Driven Data Management for Microservices: (https://www.nginx.com/blog/event-driven-data-management-microservices/)
– Focusing on Events: (https://martinfowler.com/eaaDev/EventNarrative.html)
– What do you mean by “Event Driven”?: (https://martinfowler.com/articles/201701-event-driven.html)

15. All contents © MuleSoft Inc.
What’s next
15
• Share:
– Tweet your pictures with the hashtag #MuleMeetup
• Feedback:
– Contact your organizer Anupam Gogoi to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
• Contacts
– mail: vsouza@avenuecode.com

16. Q&A

17. See you next time
Please send topic suggestions to the organizer