Patterns for Building Event-driven Web & Mobile App Backends
summary
Three interaction types are defined for client-server UX: real-time events, long-running processes (over 30 seconds) and push notifications. Concrete patterns use AppSync + EventBridge + DynamoDB streams, API Gateway WebSockets, and IoT Core MQTT topics. A React demo with an order simulator implements four backend patterns (all working), pattern two (EventBridge→AppSync direct) shows the lowest latency, and sample code lives in github aws-samples/eventdriven-frontend-patterns.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:30User interfaces
- 12:11Real-time events Pattern 1
- 20:18Real-time events Pattern 2
- 26:06Real-time events Pattern 3
- 29:02Real-time events Pattern 4
- 30:55Demo
- 32:59Bonus pattern
- 33:26Long running processes
- 37:13Push (notification) events
- 42:04Outro
related talks
41mModel-View-Websockets
37mBuild next-gen applications with event-driven architectures
56mDesigning Event-Driven Applications to Improve Scalability
31mBest Practices for Architecting Server-Driven Web/Mobile Apps
40mCloud architecture patterns, how to implement them in a serverless way
19mThe Eventful API: Rethinking Frontend State from the Server Down
39mBuilding next-gen applications with event-driven architecture
35mConvergence of Serverless APIs & Compute