Kochi Mulesoft meetup 02

1. [Kochi] MuleSoft Meetup Group
1. Evolution of Integration
2. Event Driven Architecture
[03-04-2021]

2. 2
Organizers
⮚ Kochi MuleSoft Meetup Leader.
⮚ 7+ Years of Experience in Integrations and API Technologies.
⮚ Certified MuleSoft Developer, Integration Architect and platform Architect
⮚ Kochi Mulesoft Meetup Leader.
⮚ 5+ Years of Experience in Integrations and API Technologies.
⮚ Certified MuleSoft Developer, Integration Architect and platform Architect.
⮚ Kochi Mulesoft Meetup Leader.
⮚ Senior MuleSoft Developer | Integration Lead
⮚ 10+ years of Integration Experience Certified Mulesoft
Developer, Certified Mulesoft Platform Architect

3. 3
● About the Speakers
Introductions

4. Evolution of integration

5. The past

6. The Past
6
Why : Systems and devices
How
• Socket programming
• RPC
• CORBA
• Message queues
• ESBs

7. The present

8. The Present
8
Why : Internet of things
How
• Message queues
• ESBs
• Rest APIs & Micro services
• GraphQL
• Events, Streams

9. The future

10. The Future
10
Why : Internet of everything
How
• GraphQL
• Events, Streams
• AI driven integration
• Human programming
interface(HPI)

11. The prophecy

12. The Prophecy
12
Why : Collective consciousness
How
• Universal programming
interface(UI)
• Always on mesh
• Intergalactic distributed
neural network

13. Event Driven Architecture
(MuleSoft iPaaS + Event
Broker)

14. Session will cover
14
• An Introduction of Integration Patterns/ Different Integration Approaches
• Why Event Driven Architecture
• The Main Challenge we are addressing wit EDA – Brainstorming.
• What is Event Driven Architecture
• Real Time API Family
• What are the MuleSoft provided Tools to Build Event Driven Architecture
• Basic EDA Implementation with MuleSoft iPaaS
• Matured & standard EDA Implementation with MuleSoft iPaaS + Event Broker (Solace)
• EDA Reference Architecture
• Any Questions ?

15. Different Integration Approaches
15
• Point to Point Integrations
• Integration Platforms (such as MuleSoft iPaaS)
• Connectors
• API/ MicroServices
• EDI
• Request – Response APIs
• Batch File Processing – (Managed File transfer)
• Event Driven communications

16. Why Event Driven Architecture
16
• “By 2022, event notifications will form part of over 60% of new
digital business solutions” – Gartner
• “By 2022, 50% of organizations managing APIs will incorporate
mediation of event notifications into their operations.”- Gartner
• “The event-driven integration approach is not the simplest to adopt,
but it can provide a means to unite multiple disparate systems to
promote technical flexibility. An event-driven approach can be used
to solve complex flows that share data and state changes across
multiple endpoints in a real-time manner.” - Gartner
• The event-driven approach differs from a data-centric integration
approach because it allows for faster sharing of granular data to
trigger an action in a consuming application.” - Gartner
• Event Driven Architecture is the key enabler of Digital
Transformation, helps unlocking the data from legacy systems and
facilitates the data movement from any to any data centre with out
limitation of which deployment model the application is following –
Industry Experts (CEO/CTO/Architects)
IT Research – Opinion on EDA

17. 18
● By default when we talk about real time API general perception is REST API.
● Just because traditional API delivers the data in real time does not make it real time API.
● Rest API is an interaction pattern or reque.st – response pattern.
● Challenges :-
○ Consumer always need to ask the provider for updates rather provider sending a notification in real time.
○ Consumer continues to ask the provider until the consumer receives the expected data / status.
○ Wastes the resources at provider side.
○ Provider need to build expensive solution and manage the load effectively to provide scalability.
○ Consumer side also becomes an expensive solution when there are cloud governor limits/rate limit policies.
The Main challenge

18. 19
A Different Approach
● REST API / Request response pattern is not the answer to every integration usecase implementation or
does not cover all scenarios.
● The value of information decreases over time.
● Events must be captured and reacted on real time to take informed & timely decisions (to increase
customer experience, to improve the quality of service or predictive maintainance etc)
● REST API request response pattern implies the consumer always initiates interaction with the API
provider. That’s how it works. So, asking to “know when it’s ready” is not possible with the REST API.
Guess what? This is exactly the value provided by event-driven APIs.
● Event Driven Architecture becomes a necessity as the amount of data increases and customers expect
better experience and data need to be processed in real time. Remember Time is always critical aspect.

19. 20
What is Event Driven Architecture
● Event-driven architecture (EDA) is a software architecture paradigm promoting the production,
detection, consumption of, and reaction to events.The value of information decreases over time –
Wikipedia
● Event-driven architecture (EDA) is a software design pattern in which decoupled applications can
asynchronously publish and subscribe to events via an event broker (modern messaging-oriented-
middleware). - Solace
● Event-driven architecture is a way of building enterprise IT systems that lets information flow between
applications, microservices and connected devices in a real-time manner as events occur throughout
your business, instead of periodically polling for updates.- Solace
● That’s why event-driven architecture, which pushes information as events happen, is a better
architectural approach than waiting for systems to periodically poll for updates, as is the case with the
API-led approach most companies take today.

20. 21
What is Event Driven Architecture - Concepts
An event can be defined as "a significant change in state".
Events are the lifeblood of the modern enterprise. Events are produced, detected, consumed and reacted upon.

21. 22
Realtime API
Real
Time
API
Publish &
Subscribe
Event
Driven API
Push API
Streaming
API
Real Time API
Event Driven API :- Event Driven is an architectural
style / design pattern that defines how a system should
respond / react to the events as they occur. Pubsub,
Streaming, Push APIs are a subset or fall under Event
Driven APIs umbrella.
Publish & Subscriber :- Event is produced only once by
Event producer, Events are published to Topics on Event
Broker. Event Broker applies subscription rules or topic
routing rules to route and deliver the event to the
subscribers.
Streaming API :- Streaming API is a consumer pattern,
defines how a consumer should receive and process
events. Example JMS listener
Push API :- Push API is producer pattern. When event is
produced, they are ready to be published to a receiver
over a connection. Example Webhooks, Notification
APIs.

22. MuleSoft Provided features for
implementing EDA
● Any Point MQ
○ AnyPoint Exchange
○ Queues
○ Management Console
○ AnyPoint MQ Connector
○ REST API
○ Data Encryption
● JMS Connector
● Custom Implementations

23. Basic EDA implementation example using
MuleSoft
Source of the images :-
https://blogs.mulesoft.com/dev-guides/how-to-tutorials/event-driven-salesforce-integration/
1. Complete Event Notification with full event Data
2. Event Only

24. Basic EDA implementation example using
MuleSoft

25. Advanced EDA implementation using MuleSoft iPaaS & Solace
PubSub+ (Dedicated Event Broker)
Solace (formerly Solace Systems) is a middleware company based in Canada, that manufactures and sells message-oriented
middleware appliances and software that routes information between applications, devices and user interfaces.

26. Event Driven Reference Architecture
Subscribers not capable of
REST, JMS & other solace
supported protocols or requires
complex mapping or protocol
bridging
Applications not capable of
REST, JMS or supported
protocols & frameworks by
dedicated Event Broker
1
Applications capable of REST,
JMS & supported protocols &
frameworks supported by Event
Broker
2 3
Subscribers capable of
receiving messages directly
using REST, JMS & supported
protocols & frameworks
4

27. 28
Thank You

28. Introduce yourself to your neighbor
Networking time

29. Thank you