Collecting Big Data at Scale with Amazon Kinesis
summary
Shows how to ingest clickstreams and CloudTrail logs into Kinesis Data Streams or Kinesis Data Firehose, using either the Kinesis Producer Library or a Kinesis agent, with microbatching and Lambda consumers. Documents concrete limits: one shard ≈1 MB/sec write (≈1,000 records/sec) and 2 MB/sec aggregate read, retention 24 hours–7 days, shard split/merge planning (doubling capacity can take hours). Demonstrates a working pipeline: CloudTrail → Firehose → S3 + Data Analytics → Kinesis Stream → Lambda → DynamoDB dashboard.
AI-written summary · about
chapters (20)
- 0:00Introduction to big data
- 3:14Real-time vs near real-time
- 7:05Kinesis vs Apache Kafka
- 12:24Kinesis producer library
- 15:34Kinesis agent for logs
- 17:43Kinesis client library
- 20:13Serverless architecture demo
- 23:25Kinesis data stream setup
- 27:25Kinesis data analytics
- 30:15Lambda function processing
- 32:40Event-driven pubsub model
- 35:55Distributed system challenges
- 39:03Enhanced fan-out benefits
- 41:15Shard scaling strategies
- 42:39Kinesis data firehose
- 45:30Evolutionary architecture
- 46:15Flight booking case study
- 51:18Netflix use case
- 53:09Firehose configuration
- 54:34Design principles summary
related talks
35mStreaming and Real-time Analytics
39mLarge scale streaming analytics
35mStreaming and Real-Time Analytics
38mServerless Data Streaming on AWS
29mThe need for speed: Data streaming architectures
53mDefine data streaming architectures & solutions to fit your needs
26mArchitecting real-time transactional data lake
23mCustomer Journey with streaming data on AWS
