Yousaf Nabi

Lessons from Our API Past: Evolving to a Resilient API Future

Is your microservice architecture secretly a distributed monolith? Learn how contract testing helps you escape the trap and deploy services with confidence.

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.

Matching moments

The cyclical nature of API design and development
01:24 MIN

The cyclical nature of API design and development

Awful APIs: A History Lesson in Industry Mistakes and Mishaps

The challenges of building and maintaining APIs
01:50 MIN

The challenges of building and maintaining APIs

API = Some REST and HTTP, right? RIGHT?!

The promise versus the reality of using APIs
03:17 MIN

The promise versus the reality of using APIs

Develop, test and run a communications application in a serverless cloud

Ensuring API and service stability with integration tests
02:19 MIN

Ensuring API and service stability with integration tests

Trunk-Based Development at Scale: Real-World Insights from a High-Traffic Luxury E-Commerce Platform

Designing APIs for trust and backward compatibility
02:43 MIN

Designing APIs for trust and backward compatibility

API‑First: How Twilio Designs for Developers - Justin Kitagawa (Twilio)

The challenge of evolving APIs without breaking changes
01:03 MIN

The challenge of evolving APIs without breaking changes

Evolving your APIs, a step-by-step approach

Using APIs to compartmentalize complexity and enable scalability
01:53 MIN

Using APIs to compartmentalize complexity and enable scalability

The Great API Debate: REST, GraphQL, or gRPC?

Building a resilient and scalable API gateway
06:47 MIN

Building a resilient and scalable API gateway

Improving Developer Happiness with GitOps

Featured Partners

Related Videos

See all videos
REST in Peace? What does the API protocol of the future look like? Or do we have it already?20:29

REST in Peace? What does the API protocol of the future look like? Or do we have it already?

Simon Auer

Awful APIs: A History Lesson in Industry Mistakes and Mishaps28:55

Awful APIs: A History Lesson in Industry Mistakes and Mishaps

James Seconde

API = Some REST and HTTP, right? RIGHT?!27:25

API = Some REST and HTTP, right? RIGHT?!

Rustam Mehmandarov

Contract Testing - How do you tame an external API that constantly breaks your tests26:02

Contract Testing - How do you tame an external API that constantly breaks your tests

Vincent Hennig & Anupam Krishnamurthy

Lessons learned from observing a billion API requests23:47

Lessons learned from observing a billion API requests

Pratim Bhosale

The Great API Debate: REST, GraphQL, or gRPC?28:16

The Great API Debate: REST, GraphQL, or gRPC?

Alexis Yushin

Evolving your APIs, a step-by-step approach28:49

Evolving your APIs, a step-by-step approach

Nicolas Fränkel

Five things in tech that matter and we have to make work17:01

Five things in tech that matter and we have to make work

Christian Heilmann

Related Articles

View all articles
DC
Daniel Cranney
Why Attend a Developer Event?
Modern software engineering moves too fast for documentation alone. Attending a world-class event is about shifting from tactical execution to strategic leadership. Skill Diversification: Break out of your specific tech stack to see how the industry...
Why Attend a Developer Event?

From learning to earning

Jobs that call for the skills explored in this talk.

Software Engineer

Software Engineer

Code Healers LLC
Hinesville, United States of America

Remote
€40-50K
Intermediate
Senior
PHP
.NET
React
+2
API Developer

API Developer

Ameresco
Charing Cross, United Kingdom

PHP
API
REST
Linux
MySQL
+11