Fran Méndez, founder of AsyncAPI, and Jonathan Schabowsky, senior architect at Solace, explain how the two companies are working together in this presentation from Gartner AADI.
3. Fran Méndez
A little bit about me
Twitter
@fmvilas
Email
fmvilas@gmail.com
PhotobyEvaMorcillo
Founder of AsyncAPI Initiative
Former APIs & Integrations Engineer at New Relic
4. Fran Méndez
A little bit about me
Twitter
@fmvilas
Email
fmvilas@gmail.com
Founder of AsyncAPI Initiative
Former APIs & Integrations Engineer at New Relic
12. The
specification
With it you can describe:
Event-driven microservices
IoT APIs and Sensors
…and actually pretty much any system that
is based on messages an/or events.
PhotobyLouisSmith
Streaming APIs
13. Tooling
Open source tools
Documentation generators
(HTML, Markdown, React, …)
Code generators
(JS, Go, Java, Python, Spring …)
Online editor
editor.asyncapi.org
Photo by Barn Images
14. It does NOT enforce
any particular protocol
However, it cares about the protocol because its
important information for clients and code
generators.
AMQP
MQTT
WebSockets
HTTP
PhotobyAxelAntasBergkvist
And any protocol you want to use…
Kafka
15. AsyncAPI enforces a common language
for everyone.
Language
It’s a basic pilar of communication
PhotobyGonardFluit
By defining a common language
everybody can easily create interoperable
tools, services and products.
16. Event Lifecycle
Take control of your Eventing lifecycle.
Photo by Boris Smokrovic
Design
Documentation
Code Generation
Testing
Event management
Monitoring
17. Event Lifecycle
Take control of your Eventing lifecycle.
Photo by Boris Smokrovic
Design
Documentation
Code Generation
Testing
Event management
Monitoring
20. Why WE need Event
Management
20
We need answers to…
• Where do you discover events/topics and the schema definition that
defines the payload?
• What logical event address (topic) do you subscribe to in order to
receive just the events you want to do something with?
• Why does a given event exist, i.e. what is it’s context and purpose. And
if you can’t figure that out…
• Who do you contact to learn more about more events and their
context/purpose?
• When will a given event be available or deprecated?
• How do developers/Architects define their event-driven application
interfaces, How do they generate code?