Building the future of event-driven architectures.
Become a financial contributor.
Become a silver sponsor with a monthly donation of $500 and get your logo under the Silver sponso... Read more
$500 USD / month
Become a gold sponsor with a monthly donation of $1000 and get your logo under the Gold sponsors ... Read more
$1,000 USD / month
Become a Platinum Sponsor with a monthly donation of $2000 and get your logo on the top of our RE... Read more
$2,000 USD / month
Top financial contributors
$64k USD since Apr 2019
$32k USD since Nov 2019
$12k USD since Jun 2019
$2k USD since Jun 2019
$1k USD since Jan 2020
$400 USD since Aug 2020
$350 USD since Jun 2019
$95 USD since May 2019
$75 USD since Jan 2020
$70 USD since Oct 2019
Transparent and open finances.
~ $48,821.17 USD
AsyncAPI Initiative is all of us
Our contributors 26
Everyone who has supported AsyncAPI Initiative. Individuals and organizations that believe in –and take ownership of– our purpose.
Event-driven & streaming APIs are more fragmented than HTTP/REST APIs have ever been. AsyncAPI is a community project to fix this. (Y)
guys at AsyncAPI are doing a great job. WS communication needs to be documented same way as the swagger does
We're on a mission to standardize message-based communication and increase interoperability of the different types of messaging systems available.
The messaging world is full of schema formats and protocols. Some of us prefer to use a combination of Google's protobuf with AMQP, or Avro with Kafka, or Avro with MQTT, or protobuf with MQTT, … you guessed it.
In production systems, it's common to find REST APIs, GraphQL APIs, and message-driven APIs working together. All of them serving as different interaction layers for the same data/operations. REST is usually defined using the OpenAPI specification, GraphQL has its own built-in schema language, and message-driven APIs now have AsyncAPI.
AsyncAPI is a common language for all the different protocols and schema formats, but we need to make it easy for developers to create new message-driven systems, in their programming language of choice. A quick calculation takes us to 120 possible combinations, assuming we create tooling for 6 programming languages (e.g., Java, Node.js, Go, Python, PHP, and Ruby), 4 schema formats (OpenAPI schemas, JSON Schema, Protobuf, and Avro), and 5 protocols (AMQP 0-9-1, AMQP 1.0, MQTT, Kafka, and WebSockets). We know it's a huge challenge, but we accept it 💪
REST APIs have OpenAPI. Messaging has AsyncAPI.