Budhaditya Bhattacharya
I am a Developer Advocate at Tyk responsible for product education, community engagement, and open-source ecosystem expansion. I am the course instructor of the API Platform engineering fundamentals programme, creator of the API platform maturity model, organiser and host of LEAP 2024 - the API observability conference, host of the All About APIs and the API hangout where he engages with developers and business leaders on all things APIs including product management, platform engineering, API security, open source and open standards.
Additionally, I am the chair of the OpenAPI Initiative's Governance Board driving initiatives for the education and adoption of the OpenAPI Specification.
Session
APIs have become the building blocks of the digital world. You never start a new project from scratch; you use APIs to build upon. So when anything fails in the API that you are using, your whole user experience crashes. When it’s slow, your whole product is slow.
This is where API observability can be the saviour! Implemented well, API observability can improve your developer and user experience. It can identify errors, surface insights, speed up troubleshooting, improve reliability and so much more.
But on the flip side, bad API observability can lead to inefficiencies, frustrated customers and missed revenue opportunities. In short, bad API observability is bad for business!
In this talk, let's explore the flip side. We will explore 7 anti-patterns to avoid when it comes to API observability - what they are, why they are bad and how to address them. This is one talk you don't want to miss!