Uploaded August 2024 | Updated September 2026, 1 week ago
There's a lot of talk about the new AsyncAPI support in Anypoint Code Builder. Still, before implementing some APIs (or services) with Event-Driven Architecture (EDA), it's important to understand why we chose this architecture. Not only that, but it's important to understand how to design our specifications properly before implementing the APIs.
In this video, you'll learn how to design some AsyncAPI specifications in Design Center that can be applied to a practical use case.
The practical example used in this video was motivated by the following article created on the official AsyncAPI site, by Dunith Dhanushka:
asyncapi.com/blog/understanding-asyncapis
---
📘 Learn more about AsyncAPI Specifications
AsyncAPI is a language that describes messaging interfaces. This open-source, industry-standard language is agnostic to any technology. AsyncAPI makes it easy to work with event-driven architecture by separating the API into three layers:
- Events: Message or data to be shared with other services
- Channels: Destination of the message to be sent or received
- Transport: Technology that transports the message, such as RabbitMQ, Kafka, or Anypoint MQ
You can create or import an API specification in API Designer. See the docs for more information:
docs.mulesoft.com/design-center/design-async-api
💻 Try it yourself with this GitHub repo:
github.com/alexandramartinez/asyncapis-accounts-email
---
💙 Connect with us
Learn more about the MuleSoft Community:
mulesoft.com/community
Follow us on YouTube:
youtube.com/mulesoftvids
Follow us on Twitch:
twitch.tv/mulesoft_community
Follow us on LinkedIn:
linkedin.com/showcase/mulesoftcommunity
🟦 Chapters:
00:00 Intro
00:17 Use Case and Architecture
01:08 Design the Account Service
05:16 Design the Email Service
07:20 Ending
There's a lot of talk about the new AsyncAPI support in Anypoint Code Builder. Still, before implementing some APIs (or services) with Event-Driven Architecture (EDA), it's important to understand why we chose this architecture. Not only that, but it's important to understand how to design our specifications properly before implementing the APIs.
In this video, you'll learn how to design some AsyncAPI specifications in Design Center that can be applied to a practical use case.
The practical example used in this video was motivated by the following article created on the official AsyncAPI site, by Dunith Dhanushka:
asyncapi.com/blog/understanding-asyncapis
---
📘 Learn more about AsyncAPI Specifications
AsyncAPI is a language that describes messaging interfaces. This open-source, industry-standard language is agnostic to any technology. AsyncAPI makes it easy to work with event-driven architecture by separating the API into three layers:
- Events: Message or data to be shared with other services
- Channels: Destination of the message to be sent or received
- Transport: Technology that transports the message, such as RabbitMQ, Kafka, or Anypoint MQ
You can create or import an API specification in API Designer. See the docs for more information:
docs.mulesoft.com/design-center/design-async-api
💻 Try it yourself with this GitHub repo:
github.com/alexandramartinez/asyncapis-accounts-email
---
💙 Connect with us
Learn more about the MuleSoft Community:
mulesoft.com/community
Follow us on YouTube:
youtube.com/mulesoftvids
Follow us on Twitch:
twitch.tv/mulesoft_community
Follow us on LinkedIn:
linkedin.com/showcase/mulesoftcommunity
🟦 Chapters:
00:00 Intro
00:17 Use Case and Architecture
01:08 Design the Account Service
05:16 Design the Email Service
07:20 Ending
