Turbocharging your Developer Ecosystem
summary
Built a production system called synapse that wires service-owned AsyncAPI files into infrastructure as code, using AsyncAPI files checked into GitHub, an API Gateway, AWS SNS-SQS + Lambda fanout and proxy Lambdas, and synapse CLI/SDK for validation, deploys and local testing. It provides event discovery on a Postman private API network, CI validation, automated provisioning and monitoring (New Relic and AWS), and separates publisher and subscriber schemas so teams can evolve events independently.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:44Synchronous APIs at Postman
- 2:12Engineering needs for async
- 3:36Why AsyncAPI was chosen
- 4:18Introducing Synapse bridge
- 5:09Synapse architecture overview
- 6:21Synapse SDK and API Gateway
- 8:09Developer lifecycle with AsyncAPI
- 9:16Synapse dashboards and monitoring
- 10:17Publisher/subscriber schema examples
- 11:20Synapse CLI validation
- 12:13Future plans and thanks
related talks
22mUsing Async API schema to define event driven architecture with AWS SNS
57mManaging Asynchronous APIs
21mUsing the AsyncAPI Ecosystem for your Event-Driven Architecture
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
22marmonizing Asynchronous Systems: NATS, CloudEvents and AsyncAPI.
42mAsyncAPI Recipes for EDA Gourmet
08h 51mAsyncAPI Conference 2021 - Day 3
21mStreamlining EDA: AsyncAPI-Driven Design, Documentation, and Testing