Quack the Duck and the API Client Talks
summary
Describes a unified API secured with signed JWT access tokens and OAuth2 flows plus a refresh-token‑in‑the‑database pattern so services can validate scopes without a central gateway. Implementation details include Spring Security, Postman for testing, and an AWS Lambda–backed Alexa skill wired into the token flow; the system runs across 330 microservices, 21 teams, ~800 deployments/week and ~15 languages, with a live Alexa demo that mostly works but sometimes misrecognizes wake words.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 7:04Otto's architecture
- 13:42API development goals
- 21:26Technical implementation
- 24:11API demo with Postman
- 28:46Alexa integration demo
- 35:40Code example & summary
- 40:24Q&A
related talks
44mThinking Asynchronously: App Integration Patterns for Microservices
24mModernise using Event-Driven Architectures
56mArchitecting Cloud Native Microservices
55mSingle Page Apps in a Microservice Architecture
28mPractical Microservices, Practical Whiskey
39mThinking Asynchronously
33mSPAs, full-stack, micro-frontends, enterprise migrations, what the quack?
40mBuilding an Application with TDD, DDD and Hexagonal Architecture...