Managing Multiple API Stacks on Serverless
summary
Hypertrack runs a serverless location pipeline using API Gateway, Kinesis stream (24h retention), Lambda for cleansing, DynamoDB for raw and RDS for device state, S3 + Athena for exports, plus REST, GraphQL (private), webhooks and SDKs as interfaces. Architecture separates processing layers from edge formats, adopts GeoJSON standard, and enforces semantic versioning and feature parity across interfaces. Early public docs and sample apps drive specification feedback; a caught limitation is AWS AppSync blocks custom scalars, forcing workarounds. Testing emphasizes end-to-end validation over per-stage emulation.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:06What is Hypertrack
- 2:08Location Services
- 2:50Architecture
- 10:04Learnings
- 10:19Layers
- 13:33Development
- 15:30Conceptual Alignment
- 18:37Engagement Model
- 21:19Developer Experience
- 22:06Adopt Known Standards
- 22:54Educate Developers
- 23:49Why
- 24:00Takeaway
- 25:19QA
related talks
49mServerless Architectural Patterns and Best Practices
25mLeveraging Serverless in Full-stack Development
48mThe future will be Serverless
18mGlobal Active-Active Serverless
51mSDK driven GraphQL
01h 18mBuilding applications with Serverless Framework ...
51mArchitecting for Hyperscale with AWS: Navigating Real-world Serverless Challenges
21mBuilding Fullstack applications on AWS