AsyncAPI Initiative
Building the future of event-driven architectures.
Contribute
Become a financial contributor.
Silver Sponsors
Become a silver sponsor with a monthly donation of $500 and get your logo under the Silver sponsors' category on our README on Github and the front... Read more
Starts at
$500 USD / month
Gold Sponsors
Become a gold sponsor with a monthly donation of $1000 and get your logo under the Gold sponsors category on our README on Github and the front pag... Read more
Starts at
$1,000 USD / month
Platinum Sponsors
Become a Platinum Sponsor with a monthly donation of $2000 and get your logo on the top of our README on Github and the front page of https://async... Read more
Starts at
$2,000 USD / month
Events
AsyncAPI at the API Specifications Conference
Top financial contributors
Organizations
$74k USD since Apr 2019
$32k USD since Nov 2019
$12k USD since Jun 2019
$2k USD since Jun 2019
$2k USD since Jan 2020
$1k USD since Jan 2021
$900 USD since Aug 2020
$350 USD since Jun 2019
$200 USD since Mar 2021
$100 USD since May 2019
Individuals
$320 USD since May 2019
$250 USD since Jun 2020
$75 USD since Jan 2020
$75 USD since Apr 2020
$70 USD since May 2019
$30 USD since Nov 2020
$20 USD since Sep 2020
$2 USD since Aug 2020
AsyncAPI Initiative is all of us
Our contributors 27
Thank you for supporting AsyncAPI Initiative.
Ably Realtime
Total contributions
$2,300 USD
Event-driven & streaming APIs are more fragmented than HTTP/REST APIs have ever been. AsyncAPI is a community project to fix this. (Y)
xyndata s.r.o.
Total contributions
$900 USD
guys at AsyncAPI are doing a great job. WS communication needs to be documented same way as the swagger does
Contributions
Recurring Contributions
JSON Schema
Payment method
AsyncAPI Initiative (Collective)
$1,914.80 left
Amount contributed
$250.00 USD / month
Contributed to date
$4,750.00 USD
Budget
Transparent and open finances.
Communication work for March 2021
by Alejandro L de Miguel • April 14, 2021
Marketing & Communication work for March
by María Barbaño González Moreno • April 05, 2021
Monthly financial contribution to AsyncAPI Initiative (Ba...
from Firecamp •
$1,914.80 USD
$110,768.06 USD
$108,853.26 USD
$23,547.57 USD
About
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.