Who needs batch these days?
summary
Compares real demos: Flink reads MySQL and writes CSV/HDFS but lacks built-in batch restartability; Spring Batch runs parallel flows importing posts/comments/users/votes with chunk size 1000, supports transactional commits, retries and restart from the exact failure point; Spark Streaming shows 1s micro‑batches ingesting tweets (firehose) to HDFS; an ETL workflow checks 24 hourly files and emails missing ones; a port scanner partitions 65,000 ports (demo scans low 500, finds ports 53/80/443). Uses hybrid streaming+batch rather than replacing batch.
AI-written summary · about
chapters (17)
- 0:00Introduction and welcome
- 2:36Shiny object syndrome in tech
- 5:46Batch vs streaming definitions
- 14:05Why move from batch to streaming
- 15:31Apache Flink demo overview
- 27:59Running the Flink ETL demo
- 36:57Spring Batch demo introduction
- 43:21Running the Spring Batch ETL demo
- 50:11Data science use cases
- 53:00Workflow orchestration with batch
- 1:01:44Running the Spring Batch workflow demo
- 1:03:49Non-interactive processing
- 1:09:27Port scanner batch demo
- 1:15:13When to choose batch or streaming
- 1:18:05Integrating batch with streaming
- 1:24:59Spring ecosystem advantages
- 1:27:48Batch's enduring relevance
