The document discusses the importance of APIs and event-driven architecture (EDA) in modern organizations, highlighting their role in creating responsive and engaging applications. It outlines key benefits of transitioning to EDA, including operational efficiency, scalability, and improved ROI, while showcasing successful case studies across various industries. The document emphasizes the need for businesses to adapt by integrating APIs and event-driven systems for better collaboration and data management.

1. APIs Vs Events
1

2. About Me
2
Family
Solution Architect at
Sandvik
Model
Dancer
Wellness Enthusiast

3. Agenda
Intro about
APIs and
Events
EDA in
detail
APIs and
Events
Business
Use cases
Future of
APIs &
Events

4. Introduction
As per IBM studies 60% of the
organizations are invested in speeding up
their investments in digital technology.
Rather than working towards a perfect end
state, they are focused on making their
organizations more responsive.
4

5. APIs and Events ?
5
Events are becoming increasingly important, as organization wants to build more engaging and data rich
applications.
Building great use experiences requires both APIs and Events.
- APIs for when the user engages the app
- Events for when the app engages the user

6. 6

7. As Consumers
We want our apps to be much more
responsive.
7

8. What is an
event?
An event is a change of state, or more
broadly anything that can be noticed and
recorded by an application or device and
shared with other applications and
devices.
8

9. 9
Why use event-
driven
architecture?
– The value of knowing about a given event, and being able
to react to it, degrades over time.
– The more quickly you can get information about events
where they need to be, the more effectively your business
can react to opportunities to delight a customer, shift
production, and re-allocate resources.
– EDA fuels real – time enterprise:
– Provides Continuous awareness – build a better picture of
your current business.
– Drives automation – Enable automation in response to
events in any given situation
– Enables adaptability – Adapt the way your business
operates based on situations you detect

10. 10
– Fortunately, with the right tools on hand the challenges discussed in
the previous section can be overcome.
Event Portal
Event Catalog
Schema Registry
Governance Area
Over coming the Challenges

11. 11
Every Ogranization is thinking in
direction of APIs and Events!

12. 12
EDA - Gravitee

13. 13
IBM – API and Event Automation

14. 14
Solace – PubSub +

15. Event-driven
architecture
Patterns
15

16. 16
– Real-Time Data Processing
– Internet of Things (IoT)
– Microservices Architecture
– Customer Experience Management
– Supply Chain management
– Health care systems
– Telecommunications
Business Scenarios

17. 17
Successful Case studies of
EDA
Netflix
Uber
Unilever
EDEKA
JobCloud

18. 18
– Payment Processing
– Customer Relationship
Management
– Supply Chain management
– Social Media Integration
– Data Analytics and Reporting
– Health care systems
– Travel and Booking Services
– Banking and Financial services
– Cloud Services
Business Scenarios of
API

19. 19
Successful Case studies of API
Implementation
Financial Services: Axis Bank
Retail: EDEKA
Healthcare: Mayo Clinic
Travel and Hospitality: Expedia
Telecommunications: Twilio
E-commerce: Shopify
Banking: Finologee

20. Current Challenges – Application A
Point to Point Integrations
20
• Each integration requires custom changes and individual
maintenance by the Application A team.
• High effort is needed to create and maintain the
integrations.
• The consuming system has to wait for the Application A
team to provide the needed data after configuring the
APIs.
• Increased load on Application A, developers as well as
the system as integration demands grow.
• As integration needs increase, maintaining and
managing these connections becomes challenging.
• Monitoring the health and performance of multiple
direct connections is more demanding compared to a
centralized integration platform.
• Difficult to scale due to the limited resources that can be
allocated toward building and maintaining integrations.
• There is a lack of centralized governance.
• Higher dependency on technical expertise.

21. Transition to Event
Driven Integration
21
 Application A publishes data to the Integration
platform in form of events whenever something
happens like Incident Created, Problem Updated etc.
 All systems interested in Application data will get it
from Integration platform thus less load on
Application A system to get data.
 Application A has full control over publishing the data
and controlling which information should be shared.
 Integration platform provides tailored integrations
with customizable data mapping features. Integration
team defines how data is transferred between
systems, allowing for a personalized integration
experience.

22. Key Benefits
22
• Decoupling: Consumer Systems are no more tightly
coupled with Application A, now they listen to events
without making direct API requests.
• Development Time Reduction: No need of custom
configuration or development at Application A end. Any
consumer interested in getting data can subscribe to
Integration platform and start receiving real time
updates.
• Operational Efficiency: Reduced operational load on
Application A teams, any consumer interested in getting
data can now subscribe to events without any
development team involvement. Application A can
publish any new data related to entities without any
coding effort.
• Scalability: As business need grows, new consumers can easily
connect with the integration platform by simply subscribing to
the relevant hub. There is no need to create or modify any API.
Business can adapt quickly to new opportunities or challenges.
• Flexibility: Event driven architecture supports diverse
consumers with different data needs, easier to adapt to
changing business requirements by enforcing Schema
mapping.
• ROI: Transitioning to event driven integration platform can
lead to a significant ROI by reducing recurring development
and operational costs, improving scalability, reducing time-to-
market, minimizing downtime, and enabling better use of
data. While there is an operational cost involved in using the
integration platform these costs are often outweighed by the
long-term savings and value generated from the increased
efficiency and flexibility that this integration provides.

23. Decoupling
Consumer Systems are no more
tightly coupled with A, now they listen
to events without making direct API
requests.
23

24. Development Time Reduction
24
No need of custom configuration
or development at A end. Any
consumer interested in getting
data can subscribe to Integration
and start receiving real time
updates. A
AS
IS
Consum
er
1
Consum
er
10
Consum
ers
A
TO
BE
Consum
er
1
Consum
er
10
Consum
ers
12 8 2
20
200
2
20
On boarding time
Development Time(hr) Total Time

25. Operational Efficiency
25
– Reduced operational load on A
teams, any consumer
interested in getting data can
now subscribe to events
without any development team
involvement. A can publish any
new data related to entities
without any coding effort.
12
8
0
2
Dev Effort

26. Scalability
26
As business need grows, new
consumers can easily connect with
the integration platform by simply
subscribing to the relevant hub.
There is no need to create or modify
any API. Business can adapt quickly
to new opportunities or challenges.
A current
A with Event Based integrations
0 50 100 150 200 250
200
0
10
100
Scalability
No of consumers Onborded Traffic on the A

27. Flexibility
27
Event driven architecture supports diverse
consumers with different data needs,
easier to adapt to changing business
requirements by enforcing Schema
mapping.

28. ROI
28
Transitioning to event driven integration
platform can lead to a significant ROI by
reducing recurring development and
operational costs, improving scalability,
reducing time-to-market, minimizing
downtime, and enabling better use of data.
While there is an operational cost involved in
using the integration platform these costs are
often outweighed by the long-term savings and
value generated from the increased efficiency
and flexibility that this integration provides.
Resource Cost A AS IS 1 consumer on
boarding
10 consumers
on boarding
400 8000
80000
COST AS IS
Cost(Kr/hr) Total Cost
Resource Cost Operation Cost Service now TO
BE
1 consumer on
boarding
10 consumers
on boarding
0
2500 2500 2500
COST TO BE
Cost(Kr/month) Total Cost

29. 29
Event-driven patterns and APIs
1. E-commerce Platforms
• Real-Time Inventory Management
• Personalized Customer Experience
2. Financial Services
• Fraud Detection and Prevention
• Real-Time Payment Processing
3. Healthcare
• Patient Monitoring and Alerts
• Appointment Scheduling

30. 30
Event-driven patterns and APIs
4. Logistics and Supply Chain
• Shipment Tracking
• Route Optimization
5. Telecommunications
• Network Performance Monitoring
• Customer Notifications

31. 31
Event Driven APIs
Event-driven APIs are designed to facilitate real-time and asynchronous communication between different
components or services in a system. Unlike traditional REST APIs, which require the client to continuously poll the
server for updates, event-driven APIs allow the server to push updates to the client as soon as an event occurs. This
leads to more efficient and responsive systems.
Here are some key points about event-driven APIs:
1.Real-Time Updates: Clients receive updates immediately when an event occurs, improving user experience and
reducing the need for constant polling.
2.Asynchronous Communication: Components can communicate without waiting for each other, which enhances
system performance and scalability.
3.Decoupling: Services can operate independently and only need to know about the events they are interested in,
which simplifies system architecture.
4.Common Patterns: Webhooks and streaming are popular patterns used in event-driven APIs.

32. 32
Event-driven API and APIs

33. 33
A History of Services and APIs

34. Summary
34
How do you conciliate an API-First strategy with an event-driven architecture approach?
With event-driven APIs.
Managing both APIs consistently is key to your success.
While REST APIs are still widely used and will continue to be important for many
applications, the rise of event-driven APIs reflects a broader trend towards more
responsive and efficient systems.
The future likely holds a hybrid approach, where both REST and event-driven APIs
coexist and complement each other.

35. Thank you