The document summarizes an event held by the Manila MuleSoft Meetup Group on AsyncAPI and addressing challenges in event-driven architecture. The agenda included an introduction, presentations on AsyncAPI and addressing challenges with event-driven architecture, a question and answer session, and a closing game. The presentation on AsyncAPI discussed how it helps solve issues with discovery, governance, and visibility in event-driven systems by providing a machine-readable specification for messaging APIs. It allows for cross-protocol documentation and addresses challenges developing and managing event-driven architectures.
3. 3
● This session will be recorded
● Please be muted during the speaker presentation
● The recording and slides for today’s presentations will be made available to all attendees
● At the end of each presentation, there will be a Q&A session
● After all the presentations, there will be a quiz game where you will get a chance to win a
training voucher from MuleSoft
○ Make sure to sign up using your REAL NAME
It makes it easier for the organizers to know who won.
○ Kindly, Go to www.menti.com and use the code 7414 2136
Housekeeping Rules
7. 7
●About the organizers:
○ Ryan Andal
○ Janos Geronimo
○ Christopher Co
○ John Romasanta
○ Yuichi John Nanasca
○ Karla Jaro
●About the sponsors:
○ Capgemini
○ MuleSoft
Introductions
A SHOW OF HANDS:
Who is new to this Meetup?
18. 18
● Karla is currently a Senior Consultant with Level 1 MuleSoft
Developer and MuleSoft Platform Architect Certifications
in Capgemini.
● She has a total of 8 years IT experience across
different industries such as Retail, Finance, and Learning
Management Systems.
● She believes that because of MuleSoft, she learned to fearlessly
embrace new technologies and keep on learning new things.
Speakers
KARLA MAE JARO
21. 21
● Agenda
○ What is Async API?
○ How does it help solve challenges in event-driven architecture?
○ How is it supported in Anypoint Platform?
AsyncAPI
27. 27
AsyncAPI
SYNCHRONOUS
COMMUNICATION
98.5% of API polls do
not return any new
information
REQUEST
RESPONSE
Failures cascade
through all the
coupled services
Response times
to the customers
are slow
Excessive coupling limits
flexibility to add new
services
30. 30
AsyncAPI DISCOVER
Y
Re-using is challenging as custom
coding creates black box
No agreed standard between
developers
What event-driven APIs does my
company have?
What info to include in the event?
Channels? Protocols?
31. 31
AsyncAPI GOVERNANC
E
Managing security Managing access management
Managing authentication
What validations?
How does IT apply rules
consistently across brokers, apps,
events?
33. 33
Developers lack visibility into existing events, their current use, and details on
how to reuse an existing event.
IT teams lack industry-standard best practices and conventions for defining
machine and human-readable event-driven APIs.
Developers need to work with multiple protocols (JMS, MQTT, AMQP, Kafka,
etc.), which can be challenging.
AsyncAPI
35. 35
AsyncAPI
The AsyncAPI Specification is a project used to describe and document
message-driven APIs in a machine-readable format.
It’s protocol-agnostic, so you can use it for APIs that work over any
protocol (e.g., AMQP, MQTT, WebSockets, Kafka, STOMP, HTTP,
Mercure, etc).
36. 36
AsyncAPI
API
Specification
Developers across the world can speak a consistent language on what
their event-driven service does
Helps address many of the challenges in the discovery section earlier like
the ability to auto generate dynamic docs for others to read
Open-source specification with support from many industry leader event-
driven players
Product managers can democratize access to events by exposing these
event-driven APIs in Anypoint Exchange
Anypoint Exchange can now act as a single source of truth for REST &
Event-driven APIs
37.
38.
39. QUESTION:
In Event-driven architecture, developers need to work
with multiple protocols which can be challenging. Which
of the following lists are ALL examples of protocols
available today?
a. JMS, MQTT, AMQP, RabbitLiner, AnypointMQ, Qpid
b. PMS, MRTT, AMQP, RabbitMQ, AnypointMQ, Kafka
c. MQTT, JMS, RabbitMQ , AMQP, Kafkan, AnypointMQ
d. AnypointStudio, JMS, MQTT, AMQP, RabbitMQ, Kafkan
e. JMS, MQTT, AMQP, RabbitMQ, AnypointMQ, Kafka
f. RabbitMQ, JMS, MQTT, AMQP, Kafka, AnypointPlatform
g. TPS, MRTT, AMOP, RabbitLiner, AnypointMQ, Kaffkka
PUT THE EXACT WHOLE ANSWER IN THE CHATBOX,
INCLUDING THE LETTER!
42. 42
AsyncAPI FUTURE
PLANS
DISCOVE
RY
IMPLEMENTATI
ON GOVERNANCE
• Async API 2.0 in Design
Center
• Auto-complete and validate as
you type
• Re-use REST schemas
(RAML data type)
• Discovery & Re-use - leverage
evented processes in your
organization
• Search across APIs
• Consumable documentation
• Discover brokers exposing
API
• For each pub/sub, auto
generate a connector in
Anypoint Studio
• For publish - message
destination
• For subscribe - become a
message source
• Register your broker , register,
and map existing published
API
• Will become self service
• As a process owner, you can
apply no code policies like for
the REST APIs
• REST + Evented APIs
will be managed by Anypoint
Platform for monitoring
46. 46
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: <URL of your Meetup site>
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?
47. 47
● Looking for speakers
● Suggest topics to the organizers
What’s next?