Getting Started with Flink for Small Teams w/ RabbitMQ and Kubernetes
summary
Walks through a concrete small-company pipeline: Twitter ingestion into a Flink job that buckets hourly analytics and bulk indexes to Elasticsearch, then explains why a growing monolithic job causes restarts, checkpointing and scaling pain and how inserting RabbitMQ as message queues decouples pieces. Uses Kubernetes on EKS with Ververica for deployment, started Flink in production after ~1 year of usage and RabbitMQ for ~4 years, reports one month to set up the cluster, now running 6 Flink jobs processing 4 million events/day and planning a future move to Pulsar.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:13Analytics for Dashboards
- 5:03Deploying it
- 9:58Combo Flink Job Sketch
- 12:35Messaging Queues
- 15:39Chaining Jobs
related talks
26mKubernetes & real-time analytics: How to connect these worlds with Apache Flink
37mSpark and Flink Running Scalable in Kubernetes #bbuzz
24mKeynote: The Easiest Way to Get Operational With Apache Flink
43mApache Flink in Production with Ververica Platform
33mFlink in Containerland
44mLets Deeploy Flink - Uncovering Hidden Depths of Yarn, Docker, Kubernetes & Beyond
22mBuilding a Kubernetes Operator for Apache Flink in Java
37mIntegrate Flink with Kubernetes natively
