search

OAGi / Score

Score
MIT License
9 stars 6 forks source link

Create AsyncAPI expression capability to support Event Driven Architecture #1316

Open dubnemo opened 2 years ago

dubnemo commented 2 years ago

https://www.asyncapi.com/

Documentation https://www.asyncapi.com/docs/reference/specification/v2.4.0 Leverages OpenAPI

Curious to understand the differences between this and callback approaches in OpenApI.

dubnemo commented 2 years ago

https://www.asyncapi.com/docs/tutorials/getting-started/coming-from-openapi

This seems to provide a high level mapping.

hakjuoh commented 1 year ago

AsyncAPI supports variety protocols such as WebSockets, HTTP, Apache Kafka, MQTT, etc. Each protocol has defined own message exchange flow, which makes the schema definition can vary. Do you have any preferences for it?

dubnemo commented 1 year ago

Let's keep this in the backlog for now. I want to review CloudEvents work first.

I would much prefer get closer to the finish line on OpenAPI. See the issue I created the other day.

And Protobuf has probably more impact than AsyncAPI.

On Thu, May 11, 2023, 1:28 PM Hakju Oh @.***> wrote:

AsyncAPI supports variety protocols such as WebSockets, HTTP, Apache Kafka, MQTT, etc. Each protocol has defined own message exchange flow, which makes the schema definition can vary. Do you have any preferences for it?

— Reply to this email directly, view it on GitHub https://github.com/OAGi/Score/issues/1316#issuecomment-1544485854, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHXOQO3SMGHJTEW2ZFPBI6TXFUVVLANCNFSM57L2IS3A . You are receiving this because you authored the thread.Message ID: @.***>