Going API First on the Google Cloud with Connexion
summary
Shows an API-first workflow that actually runs: an OpenAPI v2 spec drives Connexion (Flask) for automatic routing, request/response validation and typecasting, deployed as a container on App Engine Flexible behind the Cloud Endpoints ESP proxy. Demo uses an in-memory petstore, successfully creates and GETs pets, enforces API keys and decodes JWT/Firebase headers, and surfaces usage/latency in the Endpoints dashboard. Caveats: Endpoints and Connexion target OpenAPI v2 (no full v3 support) and using Endpoints drops the embedded Swagger UI.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:08What is API first
- 7:37OpenAPI specification basics
- 12:38Introducing Connexion framework
- 17:16Connexion demo walkthrough
- 21:15Hosting on Google App Engine
- 23:27Google Cloud Endpoints overview
- 25:18Cloud Endpoints architecture
- 27:53Authentication methods in Cloud Endpoints
- 30:24App Engine and Endpoints setup
- 32:11Authentication demo
- 35:24Monitoring with Cloud Endpoints
- 36:29Caveats and limitations
- 38:15API first strategy and conclusion
- 39:36Q&A
related talks
29mBringing OpenAPI to devOps
31mWeb API Mashups in a Python Application
54mManaging APIs using Cloud Endpoint on GKE
01h 00mModern API Versioning and Enterprise Ready AI Enablement with Spring Cloud Gateway
25mAPI Management from a Network Engineer's perspective
35mAPI-First! Contract-First! Make API development great again!
59mDriving better outcomes through API first development
30mGenerating docs from APIs