Giri Venkatesan - Event APIs: APIs for Event-Driven Architecture
What is your experience with designing and building APIs?
Involved in designing and implementing APIs for over 10+ years. My domain expertise is in Messaging & Event-Driven Architecture. In this domain, over and above the classic REST APIs, we have been promoting asynchronous APIs, aka Event APIs, with a new standard called AsyncAPI. I am passionate about Event-driven APIs and see how they can evolve alongside synchronous APIs and standards. I am part of the CTO team that works extensively on AsyncAPI and our Event API products that we will roll out in the coming months.
While creating API Designs, implementing and / or consuming and testing them, what challenges have you faced / are facing?
Somewhat specific to EDA - the following or some of the topics that are crucial and challenging in consuming/testing asynchronous APIs.
- Schema versioning, validation, and management
- Server-side vs Client-side responsibilities
- Message exchange patterns
- Observability
- Support for Open Protocols & Standards
What lessons have you learned with regards to designing and testing APIs?
Interestingly, it is a complex activity in the EDA context - especially with the need to support different protocols (MQTT, AMQP, JMS, WS, and others), frameworks (NodeJS, Spring Cloud Stream), iPaas (MuleSoft, Booming, and others) and various languages.
AsyncAPI & CloudEvents has made Event-driven API design and testing somewhat easy.
What do you plan to learn /explore at this conference?
Learn from the API experts in this focused group and exchange ideas.
How do you plan to contribute?
A talk, presentation, or workshop, whatever is appropriate with the organizers' approval. But, most likely as an observer and learner - look forward to connecting with people and getting a grasp of the API landscape.
Call for Papers CLOSED
Ended on Oct 30 '22 11:59 PM IST
In our experience, having participants write a position paper before coming to the conference leads to better discussion because people have thought about what they want from the conference. Last thing we want is to spend half of the conference time figuring out what you want to figure out.
A Position Paper is a simple paragraph which answers the following questions:
- What's your experience with designing and building APIs?
- While creating API Designs, implementing and / or consuming and testing them, what challenges have you faced / are facing?
- What lessons have you learned with regards to designing and testing APIs?
- What do you plan to learn /explore at this conference?
- How do you plan to contribute?
* Note that the above questions are just pointers, you don't have to answer each one point by point.
