Talk about APIs and not talk about versioning, at the very least not mention the word “versioning” is impossible. APIs present a strange dichotomy. One one hand you have a product which helps software developers to integrate with. On the other hand, your product is also the entry point to data. Whilst bug fixing a product happens with versions, we have the contradiction with APIs where ensuring a proper versioning strategy is required to make sure that the API remains functional and most importantly the clients consuming your API remains functional.

Talk about APIs and we have 3 very different API paradigms - Http APIs, gRPC and GraphQL. What are the basics of the three api paradigms and what do we need to know to come up with an API versioning strategy? Do we have any in-built support from the API paradigm itself? How can you be smart about API Versioning? Know answers to these questions in my session where I take you through the world of API versioning with code demos!