Master the skills the job market is actually hiring for.

Follow a job-market-audited Role Path, move through a discipline end-to-end with a Career Pathway, or pursue a university-benchmarked Academic Certificate — each with a Basic → Intermediate → Advanced ladder, direct video learning bridges and a capstone proof-of-work project.

Apache Kafka & Real-Time Streaming Engineering Bootcamp Certificate

Not Started0 / 10 complete

Open a video or resource link, watch it, then check its box to track your progress and unlock what comes next.

10 lessons1 capstone project

Search Live Openings

We don’t have a direct job-board feed matched to this one yet, so here are real, live US job searches for “Apache Kafka & Real-Time Streaming Engineering Bootcamp Certificate” instead.

Bootcamp Mastery Certificate B38

Build event-driven systems that survive scale, schema change and failure. Start with Tim Berglund's cohesive Kafka foundation, refresh the architecture with Confluent's 2025 Kafka 101 series, then deepen internals and stateful stream processing with Jun Rao and Apache Flink.

Benchmark: Confluent publishes the Apache Kafka Fundamentals, Kafka 101, Kafka internals and Flink learning videos publicly. Zuyini curates these free videos and applies its own independent build-and-proof completion rubric; this does not represent a Confluent- or Apache-issued credential or endorsement.

Core Video Sequence

01 — Long-form Apache Kafka fundamentals

02 — Topics, partitions, records + retention

03 — Brokers, clusters + KRaft metadata

04 — Producers, keys + delivery behavior

05 — Consumers, offsets + consumer groups

06 — Kafka Connect + integration ecosystem

07 — Schema Registry + compatibility contracts

08 — Stream processing: Kafka Streams vs Flink

09 — Kafka internals: throughput, rebalance + KRaft

10 — Stateful streaming bridge: Apache Flink 2025

Build-Along Checkpoints

  • Checkpoint 1: Run Kafka locally or in a free managed environment; create topics with an explicit partition/retention plan and document ordering guarantees.
  • Checkpoint 2: Build an idempotent producer and a consumer group; test key-based ordering, offsets, retries and duplicate/failure scenarios.
  • Checkpoint 3: Introduce Schema Registry with Avro/JSON Schema/Protobuf; evolve a contract and prove backward/forward compatibility behavior.
  • Checkpoint 4: Connect one external source or sink with Kafka Connect and show replayability plus dead-letter/error handling for bad records.
  • Checkpoint 5: Build one stateful stream transformation using Kafka Streams or Flink: filter/join/aggregate/window with event-time or state semantics.
  • Checkpoint 6: Instrument lag, throughput, errors and processing latency; inject broker/consumer/dependency failure and demonstrate safe recovery.

7-Day Independent Capstone

  • Day 1: Define events, topic ownership, keys, partitions, retention, expected throughput/latency and schema-evolution policy.
  • Day 2: Implement producers and a scalable consumer group; verify ordering, offset commits, retry behavior and duplicate handling.
  • Day 3: Add Schema Registry and perform one compatible schema evolution plus one intentionally incompatible test.
  • Day 4: Integrate an external data source/sink with Kafka Connect and prove replay from a known offset or source position.
  • Day 5: Add stateful stream processing with a join/window/aggregation and validate event-time/state behavior on edge cases.
  • Day 6: Add metrics/alerts for lag, throughput, failures and latency; inject a broker/consumer outage or poison event and recover.
  • Day 7: Publish repo, architecture/event contracts, benchmark, failure timeline, replay proof, dashboards, demo and operations runbook.

Kafka - Produce, Consume, Process & Recover

Ship a real-time event platform rather than a hello-world producer. Completion requires partition/key design, producer/consumer correctness, schema governance, external integration, stream processing, observability and proof that the system recovers safely from failure.

Proof Rubric — What Must Be Shown

  • EVENT MODEL:
  • DELIVERY: Topic/key/partition + ownership rationale Offsets, retries + duplicate semantics
  • SCHEMAS: Compatibility + versioned contracts
  • INTEGRATION: Connect source/sink + replay evidence
  • PROCESSING:
  • SCALE: Stateful join/window/aggregate correctness Throughput, lag + partition evidence
  • RELIABILITY: Failure injection + recovery proof
  • OPERATIONS: Metrics, alerts + incident runbook