Slides from Stockholm Mulesoft Meetup #3 Author: Matheus Hermsdorff

1. All contents © MuleSoft, LLC
Matheus Hermsdorff, Principal Solutions Engineer
Stockholm Meetup - Evented APIs
12.00 - 12.20 - 20 min
May , 2022

2. All contents © MuleSoft, LLC
MuleSoft Safe Harbor Statement
This presentation contains forward-looking statements. All statements other than statements of historical fact contained in this
presentation, including statements as to future results of operations and financial position, business and growth strategies,
market opportunities, planned platform features, customer acquisition and retention, and plans and objectives of management
for future operations of MuleSoft, Inc. (the “Company”) are forward-looking statements. These statements involve known and
unknown risks, uncertainties, assumptions and other factors that may cause the Company’s actual results, performance or
achievements to be materially different from any future results, performance or outcomes expressed or implied by the forward-
looking statements. These risks, uncertainties, assumptions and other factors include, but are not limited to, those related to
business and financial performance, ability to attract and retain customers, ability to enhance our platform and services and
develop new features, solutions and services, ability to respond rapidly to emerging technology trends, ability to execute on
business strategy, ability to compete effectively and ability to manage growth. Moreover, the Company operates in a very
competitive and rapidly changing environment, and new risks may emerge from time to time. It is not possible for the
Company to predict all risks, nor can the Company assess the impact of all factors on the business or the extent to which any
factor, or combination of factors, may cause actual results or outcomes to differ materially from those contained in any
forward-looking statements. In some cases, you can identify forward-looking statements by terms such as “anticipate,”
“continue,” “expect,” “explore” “intend,” “plan,” “potential,” “predict,” “project,” or “target” or the negative of these terms or
other similar words. These statements are only predictions. The Company has based these forward-looking statements largely
on its current expectations and projections about future events and financial trends that it believes may affect its business,
financial condition and results of operations. Also, these forward-looking statements represent the Company’s estimates and
assumptions only as of the date of this presentation. The Company assumes no obligation to update any forward-looking
statements after the date of this presentation. This presentation also contains estimates and other statistical data made by
independent third parties and by the Company relating to market size and growth and other industry data. These data involve a
number of assumptions and limitations, and you are cautioned not to give undue weight to such estimates. The Company has
not independently verified the statistical and other industry data generated by independent third parties and contained in this
presentation and, accordingly, it cannot guarantee their accuracy or completeness.

3. What does that mean for my
solution then?

4. All contents © MuleSoft, LLC
The life cycle of a Mule application

5. All contents © MuleSoft, LLC
Event based integration could be better supported
How to model events?
How to consume events?
How to do mapping?
How to configure my broker?
How to unit test events?
How to manage my brokers
How to apply policies to events?
How to discover events, request and
response channels?

6. All contents © MuleSoft, LLC
Improvements
AsyncAPI - a spec for Events and Channels
● Open source initiative to make working with Event-Driven
Architectures (EDA) as easy as it is to work with REST APIs.
● Enables automation and formalize Evented API documentation and
code generation.
● Protocol-agnostic (AMQP, MQTT, WebSockets, Kafka, STOMP,
HTTP, etc)
● Enables API discovery and event management.
● A specification defining the interfaces of an async API. Like
OpenAPI (aka Swagger) and RAML do for REST APIs.
Available now

7. All contents © MuleSoft, LLC
Improvements
API designer and mock
● Craft Evented APIs with the
AsyncAPI spec.
● Re-use schemas created from REST.
● Render high quality documentation.
Available now

8. All contents © MuleSoft, LLC
Improvements
Documentation
Publish spec to Exchange
Available now

9. All contents © MuleSoft, LLC
Improvements
Exchange - Discover & Reuse the APIs
● Search and find both REST payloads and Events.
● Discover & Re-use Evented APIs through high quality
documentation.
Available now

10. All contents © MuleSoft, LLC
Improvements
Easily discover & implement event processors in Studio
● Scaffolded source or
destination connectors
created from the AsyncAPI
spec
● Re-use any Evented API on
Kafka / AMQP / JMS / MQ
using simple pub and sub
contracts.
● Leverage meta-data such
as event schema for easy
development in studio.
Roadmap

11. All contents © MuleSoft, LLC
Improvements
Step 1: Evented-API Discovery
● Subodh opens up Studio
● Finds a connector in
Mule Palette
● Similar as the REST
Connector functionality
today
Roadmap

12. All contents © MuleSoft, LLC
Improvements
Step 2: Implementation Begins
● Drags method of choice as a component
○ Subscribe becomes a flow source
○ Publish becomes a destination
Roadmap

13. All contents © MuleSoft, LLC
Improvements
Step 3: pre-filled configuration
AsyncAPI bindings based configuration
Roadmap

14. All contents © MuleSoft, LLC
Improvements
Step 4: Leverage Data-sense
Roadmap

15. All contents © MuleSoft, LLC
Improvements
Step 4: Leverage Data-sense
Roadmap

16. All contents © MuleSoft, LLC
Improvements
Step 4: Leverage Data-sense
Roadmap

17. All contents © MuleSoft, LLC
Improvements
Documentation
After deployment, you map instances
to API like you do in API Manager
Roadmap

18. All contents © MuleSoft, LLC
Improvements
Deploy & Monitoring APIs
Metrics Alerts Payload search
Experience APIs
Process APIs
Mobile app
Website
System APIs
REST Web
Services
Evented
API
Services
Data lakes
Databases
IOT
Devices
Roadmap

19. All contents © MuleSoft, LLC
Summary of capabilities available
How to model events?
How to consume events?
How to do mapping?
How to configure my broker?
How to unit test events?
How to manage my brokers
How to apply policies to events?
How to discover events, request and
response channels?

20. All contents © MuleSoft, LLC
Before and After Evented API
Before - Point to point evented
integrations
logic
Kafka
Connector
AMQ
Connector
Broker1 Broker2
● Hard coded connectors.
● Required knowledge of underlying
broker.
● No insight into metadata such as event
shape, event list or other channels.
After - Reusable evented integrations
logic
API 1
Connector
API 2
Connector
Anypoint Platform
Broker1 Broker2
● Broker abstracted from the developer.
● No knowledge of underlying broker
required.
● Event schema and list of channels
exposed during design.

21. All contents © MuleSoft, LLC
Thank you

22. All contents © MuleSoft, LLC
Improvements
Securing & Managing APIs - API Gateway
Resilience
Security
QoS settings
Transformations
Automated
Pub & Sub
Policies
API manager
REST
Evented
Gateways
Kafka
amqp
Roadmap

23. All contents © MuleSoft, LLC
Improvements
Mock up - Apply no code pub/sub policies on channels
Automated Policies
API Administration
API name Version Status ClientApps Type
flightStatus v2 Active 7302 Async/Kafka
Gate Status v3 Active 1021 Async/AMQP
Booking v2 Active 400
REST
Statistics v1 Active 1 REST
flightCont v2 Active 80 REST
3 instances
rtf-us-west
rtf-ap-south
rtf-staging
Manage
Alerts
Contracts
Policies
SLA Tiers
Settings
flightStatus rtf-us-west
API Status: Active Asset Version: 1.0.0Latest Type: AsyncAPI/Kafka
API level policies
Apply New Policy
Select Policy
Policies Requires
Oauth 2.0 access token enforcement using external IDP ---
Configure
Method & Channel conditions
Apply configurations to all API methods & channels
Apply configurations to specific methods & channels
Channel regex Methods
flight* Publish
+ add Condition
Apply
API Manager
Roadmap