Last year, I had the pleasure to present in the AsyncAPI conference on the topic of documenting Socket.IO APIs.

Below, you can find the recording as well as the slides of my talk. Any questions, or comments you may have, feel free to reach out to me at dimitrios@dedouss.is.

# Recording

# Slides

https://dedouss.is/talks/asyncapi-conf/

# Abstract

Socket.IO has evolved from a JavaScript library for realtime web applications to a language agnostic protocol enabling duplex, event-driven communication. In spite of its maturity and wide adoption across the industry, the Socket.IO ecosystem is still lacking support for documenting APIs in a standardised manner. The rise of the AsyncAPI specification presents itself as a great opportunity to finally tackle this problem. In this talk, Dimitrios is going to showcase how the Socket.IO protocol can be modelled through AsyncAPI, followed by a step-by-step tutorial involving the creation of a specification YAML file, given an existing Socket.IO API. The final part of this talk will be dedicated to Asynction, a Socket.IO micro-framework written in Python, that is entirely driven by the AsyncAPI specification. Even though this presentation focuses on Socket.IO, it serves as an example of how one could express any event-driven protocol using AsyncAPI.