Yousaf Nabi
Lessons from Our API Past: Evolving to a Resilient API Future
#1about 3 minutes
Understanding the high stakes of modern API failures
Critical failures in APIs can cause massive disruption, as seen in real-world examples of zombie APIs, insecure design, and knowledge loss.
#2about 3 minutes
How microservices increased system complexity and failure points
The evolution from waterfall monoliths to agile microservices created a "service death star" with numerous potential points of failure.
#3about 2 minutes
Navigating the headwinds and barriers of microservice sprawl
Teams face challenges with microservice adoption due to a lack of skills, system complexity, and pressure to deliver features quickly.
#4about 5 minutes
Why traditional testing methods fail for microservice architectures
Integrated and end-to-end tests become slow, flaky, and hard to debug, providing feedback too late in the development cycle.
#5about 7 minutes
The role and limitations of API specifications
While OpenAPI and AsyncAPI provide a common language, they don't solve provider drift, consumer drift, versioning, or governance challenges.
#6about 3 minutes
Introducing contract testing for safe API evolution
Contract testing validates interactions between services in isolation, providing fast feedback without the need for integrated environments.
#7about 2 minutes
Implementing a safe deployment workflow with Pact Broker
The Pact Broker stores contracts and enables the `can-i-deploy` tool to verify compatibility before deploying services independently.
#8about 2 minutes
Gaining early feedback with advanced contract testing techniques
Bi-directional contract testing and design-time checks in tools like Swagger Editor provide impact analysis before any code is written.
#9about 2 minutes
Preparing for the future with AI agent workflows
The Arazzo specification helps document and compose complex, deterministic API workflows to manage the rise of AI agent consumers.
#10about 1 minute
Using contract testing to build a version-free API
By understanding consumer usage through contracts, teams can manage breaking changes, combat Hyrum's Law, and reduce the need for API versioning.
Related jobs
Jobs that call for the skills explored in this talk.
Featured Partners
Related Videos
20:29REST in Peace? What does the API protocol of the future look like? Or do we have it already?
Simon Auer
28:55Awful APIs: A History Lesson in Industry Mistakes and Mishaps
James Seconde
27:25API = Some REST and HTTP, right? RIGHT?!
Rustam Mehmandarov
26:02Contract Testing - How do you tame an external API that constantly breaks your tests
Vincent Hennig & Anupam Krishnamurthy
23:47Lessons learned from observing a billion API requests
Pratim Bhosale
28:16The Great API Debate: REST, GraphQL, or gRPC?
Alexis Yushin
28:49Evolving your APIs, a step-by-step approach
Nicolas Fränkel
32:28Building APIs in the AI Era
Hugo Guerrero
From learning to earning
Jobs that call for the skills explored in this talk.
Software Engineer, API Governance
Remote Woman
Paris, France
Remote
Intermediate
API
REST
Python
Microservices
Java Developer Mid - APIs - API First - scrum,agile - remoto (*A)
BETWEEN TECHNOLOGY
Municipality of Madrid, Spain
API
Java
gRPC
Scrum
Redis
+3