Real-time stream data processing with fully managed AWS Kinesis services
summary
Telesign migrates SMS transaction and completion records from RabbitMQ into Kinesis Data Streams and runs hosted Apache Flink via Kinesis Data Analytics (Apache Flink) to join events, aggregate by country/operator with one‑minute tumbling windows, and persist results to RDS Postgres for live dashboards. The pipeline enforces exactly-once semantics and moves end-to-end latency from ~30–60 minutes down to 3–4 second latency, using CloudWatch for monitoring and a custom Kinesis publisher.
AI-written summary · about
chapters (17)
- 0:00Introduction and agenda
- 3:24SMS Verify use case
- 8:40Old architecture limitations
- 10:20Goal of stream processing
- 11:07What is stream processing
- 13:08Batch vs stream processing
- 13:52Stream processing architecture
- 15:47Challenges in stream processing
- 16:42AWS Kinesis services overview
- 17:33Kinesis Data Streams explained
- 19:40Kinesis Data Analytics
- 21:12New architecture with Kinesis
- 22:47Achieved latency improvements
- 23:09Flink applications details
- 24:30Apache Flink framework
- 26:35Flink data flow and APIs
- 29:15Q&A session
related talks
30mBuild and run streaming applications with Apache Flink and Amazon Kinesis Data Analytics
23mCustomer Journey with streaming data on AWS
35mStreaming and Real-time Analytics
53mDefine data streaming architectures & solutions to fit your needs
29mThe need for speed: Data streaming architectures
35mStreaming and Real-Time Analytics
39mLarge scale streaming analytics
55mCollecting Big Data at Scale with Amazon Kinesis
