Motivation

Orchestration is particularly important when it comes to dealing with distributed architecture styles like microservices. At its core, orchestration is a pattern that favors a centralized application workflow. 

With synchronous APIs (OpenAPI), there is a request/response pattern, wherein a request is made and the application awaits the response before moving on. Asynchronous APIs, by comparison, most often use a publish/subscribe (often referred to as pub/sub) model, wherein an application subscribes to a topic and then the API provides updates to all subscribers whenever any message is posted to that topic. With an asynchronous API, the key factor is that the application continues moving forward, not awaiting a response, and these types of APIs have become the backbone for serverless and microservices architectures.

Goal

Enable orchestration of AsyncAPI microservices in workflows

Scenarios

As a developer, I need to call a service defined by AsyncAPI descriptor (yaml) so that the workflow can communicate with that service asynchronously (with publish and subscribe events)

Expected outcomes

Workflows can use operation state with AsyncAPI functions

Follow AsyncAPI initiative: https://www.asyncapi.com/ 

We recommend the following message brokers: Only Kafka is fully supported. HTTP is partially supported

Security is limited to: No security available

Version of AsyncAPI: 2.0