Status update (week 13, 2019)
Pozdrowienia, przyjaciele! This week is a special one. We just finished implementing all the features of version 2.0.0 that affect the specification 🎉
It means we’re now entering the review period. We encourage everyone familiar with the specification to start reviewing the new version and submit your questions and suggestions to our Github repository. We make AsyncAPI together!
If you’re not yet that familiar with the specification, don’t worry, we’ll be publishing lots of tutorials and documentation soon, from “hello world” to real use cases. Stay tuned!
Latest changes in the specification
- Rename scheme as protocol. It’s been a source of confusion for quite a long time now. “Scheme” is also used for security schemes and the word is very similar to “schema” (in the end most of us are not native English speakers.) No more confusions, call them protocols!
- Remove the stream object. Now that we have
protocolInfoobjects and channels, there’s no need to keep using the stream object. This doesn’t mean we get rid of the support for HTTP streaming APIs; on the contrary, we’re preparing the foundations to construct a bigger building. Check out the example in the pull request to learn more about the change. - Add support for RAML-like traits. RAML has been offering a feature called traits for a long time and they’ve proven to be very useful. Avoid repetitive blocks in your AsyncAPI documents. Use traits!
Donate
And last but not least, we’re running a sponsorship campaign. We’ve got different tiers so that everybody can show their love! ❤️
Donate here. Help Open Source projects.
“Great things are done by a series of small things brought together.”
— Vincent Van Gogh
See you next week, folks! 👋
