Summary of "Building Software Better: API Lifecycle Management for Developers • Erik Wilde • GOTO 2024"

Building Software Better: API lifecycle management

Erik Wilde — GOTO 2024

Treat APIs as products: design for consumers (outside‑in), describe them clearly, version them for evolvability, and bake good practices into platforms so teams can scale API development and reuse. Use machine‑readable API descriptions (OpenAPI, GraphQL, AsyncAPI) across the lifecycle for design, docs, testing, codegen, governance and automation.

Core message

• Treat APIs as products: focus on consumers, business value, evolution and minimal breaking changes.
• Use API descriptions as the shared machine‑readable language across the lifecycle (design, docs, tests, codegen, governance).
• Platform engineering and API management are complementary: embed best practices (linting, mock servers, tests, rules) in platform tooling to speed delivery and improve consistency.

Key concepts and practices

API product mindset

• Identify who the API is for and what value it delivers (internal vs external).
• Prefer outside‑in design (value/business aligned) over inside‑out (implementation driven).
• Design for evolution to avoid breaking consumers.

API descriptions

• Primary description languages:
  • OpenAPI (REST)
  • GraphQL (query‑style APIs)
  • AsyncAPI (event‑driven)
• Descriptions enable tooling: autogenerated docs, SDKs, validation, testing, platform rules and automation.

API lifecycle stages

• Example lifecycle (WSO2 model): create → secure → document → test → version → publish → promote → monetize → retire.
• Many stages are toolable using OpenAPI and related specs.

API workflows

• Aro (new spec from the OpenAPI Initiative): describes multi‑API workflows/business processes in a machine‑readable way.
• Early stage but promising for linking docs, tests, SDKs to business flows.

Versioning and evolvability

• Use schemas and explicit contracts to support testing and automation.
• Design APIs to evolve without breaking existing consumers.

Platform engineering

• Build “golden paths”, templates and automated governance (linting, CI checks) so teams produce consistent APIs at scale.
• Embed best practices in platform tooling to reduce friction.

API monetization and business models

• APIs often create indirect value (audience, partner integrations, added services) rather than direct per‑call revenue.
• Examples:
  • Walgreens: photo‑printing kiosks exposed via API to partner apps (revenue share + store traffic).
  • Authentication integrations (Google, Twitter/X): drive signups and audience rather than direct revenue.

API gateway evolution

• Gateways have become lighter and more modular; security and ecosystem tools are composed around core gateways.

Tools, techniques, and sample tooling

• Description languages: OpenAPI, GraphQL, AsyncAPI.
• Linting/standards enforcement: Spectral, Vacuum, and other linters.
• Mocking: generate mock servers from OpenAPI to prototype UIs and get early feedback.
• Testing techniques:
  • Schema validation
  • Fuzzing (send borderline/invalid inputs to test robustness)
  • Greasing: deliberately vary behavior to expose fragile client assumptions and force compatibility hardening
• API management ecosystem: many vendors and specialized tools (see API Days ecosystem maps).
• Emerging spec to watch: Aro (API workflow spec from the OpenAPI Initiative).

Guides, resources, and tutorials referenced

• Speaker’s slides: interactive web slides with links (publicly available).
• Speaker’s YouTube channel: “Getting APIs to Work” — interviews and tutorials on API technologies and tools.
• Background reading: ProgrammableWeb resources and a ~60‑page report with examples of API business models.
• Watch for tooling growth around the Aro workflow spec.

Actionable takeaways

1. Describe APIs early with OpenAPI (or the appropriate language) to unlock documentation, tooling and governance.
2. Treat APIs as products: interview consumers, prototype with mocks, enforce patterns with linters, and version carefully.
3. Invest in platform engineering: provide golden paths, CI gates and automated checks to scale consistent API practices.
4. Use testing techniques (schema validation, fuzzing) and consider greasing to harden compatibility.
5. Think broadly about API value — many successful strategies create indirect business value (audience, integrations) rather than only charging per call.

Main speaker and notable sources

• Main speaker: Erik Wilde (principal consultant; OpenAPI Initiative ambassador)
• Referenced organizations/people/specs:
  • OpenAPI Initiative (OpenAPI, Aro)
  • SmartBear (Swagger origin)
  • WSO2 (lifecycle model)
  • API Days (ecosystem map)
  • Gartner / Mark O’Neal (gateway evolution)
  • ProgrammableWeb
  • Walgreens, Stripe, Twitter/X (business‑model examples)
  • Platform engineering community

(Slides and the speaker’s channel include step‑by‑step examples, demos and links to the tools mentioned.)

Category

Technology

---

Share this summary

Share on X/Twitter Share on Facebook Share on LinkedIn Share on Reddit Share on WhatsApp Share on Telegram

---

Is the summary off?

If you think the summary is inaccurate, you can reprocess it with the latest model.

Reprocess summary

Video