# MASTER DEVELOPMENT PROMPT: KAFKA IN EVENT-DRIVEN ARCHITECTURE — COMPLETE EDUCATIONAL EXPLAINER VIDEO
## 1. Project Overview
**Project title:** Kafka in Event-Driven Architecture: From Concepts to a Working Practical Lab
**Objective:** Develop a professional, visually engaging, technically accurate educational explainer video based on the supplied PowerPoint presentation, *Kafka_Event_Driven_Architecture_Theory_Practical.pptx*.
The video must teach students how event-driven architecture works, why Apache Kafka is used, how its components communicate, how reliability and scalability are achieved, and how to implement a working Kafka producer-consumer example using Python.
The video is intended for computer science students studying Advanced Software Architecture and Design (ASAD), distributed systems, microservices, and software architecture.
**Primary audience:** Undergraduate and postgraduate computer science students, particularly M.Sc. Computer Applications and Information Technology students.
**Teaching approach:** Explain every concept using a combination of:
- Animated architecture diagrams.
- Real-world business scenarios.
- Step-by-step data-flow animations.
- Clearly highlighted technical terminology.
- Code demonstrations with narration.
- Terminal demonstrations and expected outputs.
- Practical comparisons and decision-making examples.
- Short knowledge checks and a concluding quiz.
Do not merely convert the PowerPoint slides into a slideshow. Develop a coherent teaching experience with animated explanations, meaningful transitions, consistent visual design, and a logical progression from foundational theory to practical implementation.
## 2. Source Material and Accuracy Requirements
Use the supplied PowerPoint as the primary source of truth.
Preserve its central terminology, learning objectives, concepts, example events, Kafka vocabulary, practical-lab structure, Python client choice, Docker-based setup, and key design trade-offs.
The video must cover the material in the following sequence:
1. Introduction and learning objectives.
2. Events, commands, and queries.
3. Event-driven architecture.
4. Direct synchronous communication versus asynchronous event-driven communication.
5. An online shopping order as a real-world example.
6. Apache Kafka fundamentals.
7. Kafka cluster architecture and core terminology.
8. Event records, JSON payloads, keys, and headers.
9. Partitions, ordering, and parallelism.
10. Partition keys and consumer groups.
11. Replication and fault tolerance.
12. Offsets, acknowledgements, delivery semantics, and idempotency.
13. Retention and event replay.
14. Real-world applications and architectural decision-making.
15. Production-readiness considerations.
16. A complete Docker and Python practical lab.
17. Consumer reliability, retries, and dead-letter topics.
18. Common misconceptions.
19. Knowledge-check questions and final recap.
Do not silently replace the presentation's technical approach with another architecture, language, library, or implementation.
When explaining implementation details, distinguish between what Kafka itself provides and what application developers must implement.
If a code example or configuration requires correction to execute successfully in a particular environment, explain the correction clearly and keep it consistent with the source material.
Do not fabricate terminal outputs, performance statistics, benchmarks, or guarantees.
## 3. Video Format and Production Specifications
Create a polished, full-HD educational video with the following specifications:
- **Aspect ratio:** 16:9 widescreen.
- **Resolution:** 1920 × 1080.
- **Frame rate:** 30 FPS
