apidays London 2024
2024-09-18..2024-09-19
London, United Kingdom
[apidays London 2019, apidays London 2023, apidays London 2024, apidays London 2025]
who it's for
api platform engineers, api architects, product managers, backend engineers, developer experience engineers, security engineers
topics
event-driven architecture with Kafka; AsyncAPI with NATS and CloudEvents; OpenAPI and mocking; LLM API load testing in CI/CD; api management federation and catalogs; api security testing blueprint; digital product sustainability measurement; api lifecycle and developer experience; deprecation-driven legacy transformation; financial api integration and settlements; geospatial open standards for APIs; domain APIs as anti-corruption layer
| title | author | length |
|---|---|---|
| From Digital Emissions Reporting to Taking Product Action | Julie Dennis, Andri Johnston | 20m |
Cambridge University Press & Assessment measures product carbon using the dmct tool for publishing workflows, AWS hosting metrics and Google Analytics for… | ||
| How to limit your cloud impact, from bare metal to AI | James Martin | 28m |
Claims that cloud moves cut emissions need context: global digital emissions sit near 4% with data centers ~1% and hardware ~75% of that, PUE averages 1.55… | ||
| Event-Driven Architecture: Unleashing responsiveness | Vijay Nadkarni | 23m |
Argues that cloud economics make event streams practical and shows a concrete pattern spectrum: event notification, delta events, state events and specifically… | ||
| Bringing the Power of APIs to Event Driven Architecture | Radhouane Jrad | 17m |
Argues that adding APIs to an existing event hub turns an unruly EDA into a governable, secure platform by acting as an anti-corruption layer that publishes to… | ||
| Renovate to Innovate: Fundamentals of transforming legacy architecture | Rashmi Venugopal | 25m |
Claim: legacy systems are a predictable byproduct of growth and are defined as systems incapable of keeping up with business requirements. Concrete strategies… | ||
| Microservices Paradise: is it possible to achieve? | Irina Kamalova | 16m |
Argues for concrete engineering rules: enforce layered services with one-way calls BFF -> flow -> stateful -> gateway, allow skipping layers but forbid lateral… | ||
| Scaling LLM APIs: Integrating Load Testing Into Your CI/CD Pipeline. | Samir Akarioh | 14m |
Shows a concrete CI/CD pipeline that packages Gatling simulations and triggers Gatling Enterprise runs from GitHub Actions workflow, using a packaged .sh to… | ||
| From Fragmentation to Federation: The Future of API Management. | Peter Mörsch | 10m |
Argues for an API catalog across vendors with at least two catalogs internal and external, a single governance dashboard that connects multiple gateway vendors… | ||
| Building APIs Together: How to Embrace a Multi-Player Strategy. | Alex Barnett | 24m |
Argues that collaborative API development is essential, not optional, and shows concrete results: adding a run-in-Postman button and importable collections… | ||
| APIs: The Hidden Power Brokers in the EU Data Act Enforcement. | David Vazquez Cortizo | 22m |
EU regulation forces IoT and finance data sharing by creating data holder and data user roles, allows public authorities free emergency access, and treats cars… | ||
| The API Lifecycle and Developer Experience for Product Managerr | Gareth Faull | 10m |
Defines two PM types: an API provider PM who treats a REST, external API as a revenue-facing product with endpoints, docs and customer beta tests, and an API… | ||
| Seamlessly Connecting Financial Giants: Partnering through API Integration. | Max Sadlowski | 16m |
Wise Platform exposes REST APIs that power 40 currencies across 160+ countries, five direct local-rail connections and 65 licences, claiming 60% instant… | ||
| The Impact of AI on APIs: Can AI replace the API Architect? | Saheed Abiola Lasisi | 31m |
Claims that generative models speed API work but do not replace judgment: AI delivers linting at design time and auto-generates docs, code snippets and SDKs… | ||
| Unleash the Power of API Management Solution | Maurizio Garzelli | 19m |
Boomi presents a SaaS control plane with agents that initiate outbound connections so no inbound holes are opened, scans API gateways to discover shadow and… | ||
| An API Security Testing Blueprint: Because Unit Tests Just Aren't Enough. | Teresa Pereira | 17m |
Claims that unit tests alone miss interactions, auth gaps and runtime flaws and offers a concrete blueprint: start by inventorying architecture, environment… | ||
| Building Cross-Exchange Trading Library With AsyncAPI | Sho Kaneko | 20m |
Claim: a reusable cross‑exchange trading library is built that generates REST and WebSocket clients from exchange docs and plugs them into a domain API so the… | ||
| Lessons from Sync API Design: What Makes A Good AsyncAPI? | Swen-Helge Huber | 18m |
Argues that good AsyncAPIs borrow three REST lessons: familiar documentation by using the AsyncAPI spec and developer portals that present Async and REST… | ||
| armonizing Asynchronous Systems: NATS, CloudEvents and AsyncAPI. | Artur Ciocanu | 22m |
A small observability platform is built with Java Spring Boot services: a demo app, a metrics agent, a data-collector and a reporter, all exchanging NATS… | ||
| Inclusive APIs: How to Extend OpenAPI for Accessibility | Patrick Brosse | 23m |
Claims that adding a small set of API-level fields to OpenAPI lets backends drive accessibility so UIs and assistive tech behave consistently. Uses… | ||
| Develop in Parallel and Ship Earlier with OpenAPI and Mocking | Tom Akehurst | 21m |
Demonstrates using WireMock Cloud with an existing Train Travel OpenAPI spec to cut feature lead time (example drops a four‑sprint flow to about two) by… | ||
| Open Standards for Getting your APIs into the Geospatial Ecosystem. | Gobe Hobona | 21m |
OGC recommends five steps: identify relevant standards, implement or deploy certified products, integrate with third-party catalogs, promote implementations… | ||
| The Arazzo Specification | Frank Kilkomins | 28m |
Arazzo defines a YAML/JSON format to deterministically describe multi‑call API workflows with inputs, parameters, steps, success/failure actions, outputs and… | ||
| nothing matches | ||