Sharing what we love: The Apache Flink story at Pinterest
summary
Pinterest replaces Kafka Streams with Apache Flink to run large-scale stream apps that power features for 478 million users, claiming reduced latency from hours to seconds by adding a Flink speed layer that buffers 24 hours (and seven days for some flows) and supports backfill/reprocess inside the app. Two engineers operate a stats pipeline launched to wide usage; shopping catalog updates go from 24 hours to 5 seconds, real-time conversion prediction improves attribution coverage, and matrix aggregation and A/B testing move from flaky to production-grade.
AI-written summary · about
chapters (7)
- 0:00Introduction to Pinterest
- 3:57Pin stats use case
- 8:27Content creator use cases
- 14:39Shopping catalog use case
- 20:02Infrastructure engineering use cases
- 22:44Lessons learned with Flink
- 24:09Closing remarks and Q&A
related talks
18mReal-time Experiment Analytics at Pinterest with Apache Flink
25mData: Moving with the flow
21mReal-time Stream Analytics and Scoring Using Apache Flink, Druid & Cassandra
15mFeature Stores: Powering Machine Learning Infrastructure with Apache Flink
27mArchitecting Sub-Second Analytics Pipelines
20mUsing Flink for Versatile Feature Engineering Pipelines
18mThe role Stream Processing plays for an Opti Channel Experience
15mData science at scale using Apache Flink: Dynamic model serving and real-time feature generation
