{"id":1132,"date":"2026-08-19T00:36:46","date_gmt":"2026-08-19T00:36:46","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/?p=1132"},"modified":"2026-08-19T00:46:54","modified_gmt":"2026-08-19T00:46:54","slug":"kafka-master-tutorials-series-1-an-introduction-of-kafka","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/kafka-master-tutorials-series-1-an-introduction-of-kafka\/","title":{"rendered":"Kafka Master Tutorials Series: 1 – An Introduction of Kafka"},"content":{"rendered":"\n

What Is Apache Kafka?<\/h1>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Learning Objective<\/h2>\n\n\n\n

By the end of this tutorial, you should be able to explain:<\/p>\n\n\n\n

    \n
  • What Apache Kafka is<\/li>\n\n\n\n
  • What an event<\/strong> means in Kafka<\/li>\n\n\n\n
  • Why Kafka is called an event streaming platform<\/strong><\/li>\n\n\n\n
  • How data moves through Kafka<\/li>\n\n\n\n
  • What producers, topics, brokers, and consumers do at a high level<\/li>\n\n\n\n
  • How Kafka is different from a database or a traditional message queue<\/li>\n\n\n\n
  • Where Kafka fits in a real production system<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    1. Start With a Simple Problem<\/h1>\n\n\n\n

    Imagine that we have a vehicle application.<\/p>\n\n\n\n

    Every few seconds, thousands of vehicles send information such as:<\/p>\n\n\n\n

    Vehicle location\nVehicle speed\nBattery percentage\nCharging status\nEngine status\nTrip started\nTrip completed\n<\/code><\/pre>\n\n\n\n
    One vehicle may produce data like this:<\/p>\n\n\n\n
    {\n  \"vehicle_id\": \"CAR-101\",\n  \"speed\": 72,\n  \"battery\": 64,\n  \"latitude\": 12.9716,\n  \"longitude\": 77.5946\n}\n<\/code><\/pre>\n\n\n\n
    Now imagine:<\/p>\n\n\n\n
    10 vehicles\n100 vehicles\n10,000 vehicles\n1,000,000 vehicles\n<\/code><\/pre>\n\n\n\n
    And many systems want this data:<\/p>\n\n\n\n
    Analytics\nAlerts\nDatabases\nMobile applications\nBilling\nMachine learning\nMonitoring\nTrip processing\n<\/code><\/pre>\n\n\n\n
    Connecting every application directly to every other application quickly becomes difficult.<\/p>\n\n\n\n
    Kafka helps solve this kind of problem.<\/p>\n\n\n\n
    \n\n\n\n
    2. What Is Apache Kafka?<\/h1>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Apache Kafka is a distributed event streaming platform.<\/strong><\/p>\n\n\n\n
    That definition contains three important ideas:<\/p>\n\n\n\n
    Distributed\nEvent\nStreaming\n<\/code><\/pre>\n\n\n\n
    We will understand each one.<\/p>\n\n\n\n
    \n\n\n\n
    3. What Is an Event?<\/h1>\n\n\n\n
    An event<\/strong> means:<\/p>\n\n\n\n
    \n
    Something happened.<\/p>\n<\/blockquote>\n\n\n\n
    Examples:<\/p>\n\n\n\n
    Customer placed an order\nVehicle changed location\nPayment completed\nUser logged in\nSensor temperature changed\nTrip started\nCharging started\n<\/code><\/pre>\n\n\n\n
    Suppose a vehicle changes its location.<\/p>\n\n\n\n
    The event could look like:<\/p>\n\n\n\n
    {\n  \"vehicle_id\": \"CAR-101\",\n  \"event_type\": \"gps_updated\",\n  \"latitude\": 12.9716,\n  \"longitude\": 77.5946,\n  \"timestamp\": \"2026-08-19T10:30:20Z\"\n}\n<\/code><\/pre>\n\n\n\n
    This Kafka record describes something that happened.<\/p>\n\n\n\n
    In everyday Kafka discussions, you may hear people call this a:<\/p>\n\n\n\n
    Event\nMessage\nRecord\nKafka message\nKafka event\n<\/code><\/pre>\n\n\n\n
    There are small technical differences in terminology, but beginners can initially think of them as pieces of data being sent through Kafka.<\/p>\n\n\n\n
    \n\n\n\n
    4. What Does Streaming Mean?<\/h1>\n\n\n\n
    Streaming means data keeps arriving continuously.<\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    10:00:01 \u2192 Vehicle A location\n10:00:02 \u2192 Vehicle B location\n10:00:02 \u2192 Vehicle C speed\n10:00:03 \u2192 Vehicle A battery status\n10:00:04 \u2192 Vehicle D location\n10:00:05 \u2192 Vehicle B charging status\n<\/code><\/pre>\n\n\n\n
    The system does not need to wait until the end of the day.<\/p>\n\n\n\n
    Events can be processed as they arrive.<\/p>\n\n\n\n
    That is why Kafka is heavily used for real-time and near-real-time systems<\/strong>.<\/p>\n\n\n\n
    \n\n\n\n
    5. What Does Distributed Mean?<\/h1>\n\n\n\n
    Kafka normally does not run as one single server.<\/p>\n\n\n\n
    A production Kafka system can contain multiple Kafka servers.<\/p>\n\n\n\n
    These servers are called:<\/p>\n\n\n\n
    Brokers<\/strong><\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    Kafka Cluster\n\u2502\n\u251c\u2500\u2500 Broker 1\n\u251c\u2500\u2500 Broker 2\n\u2514\u2500\u2500 Broker 3\n<\/code><\/pre>\n\n\n\n
    Together, these brokers form a:<\/p>\n\n\n\n
    Kafka Cluster<\/strong><\/p>\n\n\n\n
    Using multiple brokers allows Kafka systems to handle:<\/p>\n\n\n\n
      \n
    • large amounts of data<\/li>\n\n\n\n
    • many applications<\/li>\n\n\n\n
    • machine failures<\/li>\n\n\n\n
    • increasing traffic<\/li>\n\n\n\n
    • high availability<\/li>\n<\/ul>\n\n\n\n
      Later in this series, we will study brokers, partitions, replication, leaders, followers, and fault tolerance in detail.<\/p>\n\n\n\n
      \n\n\n\n
      6. The Simplest Kafka Architecture<\/h1>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      The easiest Kafka architecture to remember is:<\/p>\n\n\n\n
      Producer\n   \u2193\n Kafka\n   \u2193\nConsumer\n<\/code><\/pre>\n\n\n\n
      More accurately:<\/p>\n\n\n\n
      Producer\n   \u2193\nKafka Topic\n   \u2193\nConsumer\n<\/code><\/pre>\n\n\n\n
      Example:<\/p>\n\n\n\n
      Vehicle Service\n      \u2193\n   PRODUCER\n      \u2193\nvehicle-events\n  Kafka Topic\n      \u2193\n   CONSUMER\n      \u2193\nAnalytics Service\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      7. What Is a Producer?<\/h1>\n\n\n\n
      A producer<\/strong> sends events to Kafka.<\/p>\n\n\n\n
      Examples of producers:<\/p>\n\n\n\n
      Vehicle application\nWebsite\nPayment service\nMobile application\nIoT sensor\nOrder service\nBackend application\n<\/code><\/pre>\n\n\n\n
      Example:<\/p>\n\n\n\n
      Vehicle\n   \u2193\nTelematics Service\n   \u2193\nKafka Producer\n   \u2193\nKafka\n<\/code><\/pre>\n\n\n\n
      The producer might send:<\/p>\n\n\n\n
      {\n  \"vehicle_id\": \"CAR-101\",\n  \"speed\": 95\n}\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      8. What Is a Topic?<\/h1>\n\n\n\n
      Kafka stores events inside topics<\/strong>.<\/p>\n\n\n\n
      A topic is similar to a named stream or category of events.<\/p>\n\n\n\n
      Examples:<\/p>\n\n\n\n
      vehicle-events\npayments\norders\ncustomer-events\ngps-updates\ncharging-events\nsystem-events\n<\/code><\/pre>\n\n\n\n
      For example:<\/p>\n\n\n\n
      Kafka Cluster\n\nTopic: vehicle-events\n---------------------\nEvent 1\nEvent 2\nEvent 3\nEvent 4\nEvent 5\n<\/code><\/pre>\n\n\n\n
      Applications know where to send or read data based on the topic name.<\/p>\n\n\n\n
      \n\n\n\n
      9. What Is a Consumer?<\/h1>\n\n\n\n
      A consumer<\/strong> reads events from Kafka.<\/p>\n\n\n\n
      Example:<\/p>\n\n\n\n
      Vehicle\n   \u2193\nKafka Producer\n   \u2193\nvehicle-events\n   \u2193\nKafka Consumer\n   \u2193\nAnalytics Service\n<\/code><\/pre>\n\n\n\n
      But Kafka becomes much more powerful when multiple applications consume the same event stream.<\/p>\n\n\n\n
                          \u2192 Analytics\n                    \u2192 Alerts\nVehicles \u2192 Kafka    \u2192 Database\n                    \u2192 Billing\n                    \u2192 Machine Learning\n                    \u2192 Monitoring\n<\/code><\/pre>\n\n\n\n
      The vehicle system sends the event once.<\/p>\n\n\n\n
      Kafka can make that stream available to many independent consumers.<\/p>\n\n\n\n
      \n\n\n\n
      10. A Real Example<\/h1>\n\n\n\n
      Suppose:<\/p>\n\n\n\n
      CAR-101 speed = 125 km\/h\n<\/code><\/pre>\n\n\n\n
      The vehicle sends:<\/p>\n\n\n\n
      {\n  \"vehicle_id\": \"CAR-101\",\n  \"event_type\": \"speed_updated\",\n  \"speed\": 125\n}\n<\/code><\/pre>\n\n\n\n
      The flow could be:<\/p>\n\n\n\n
      CAR-101\n   \u2193\nTelematics API\n   \u2193\nKafka Producer\n   \u2193\nTopic: vehicle-events\n   \u2193\n+--------------------------+\n|         Kafka            |\n+--------------------------+\n   \u2193        \u2193        \u2193\nAlerts   Database  Analytics\n<\/code><\/pre>\n\n\n\n
      The alert service sees:<\/p>\n\n\n\n
      speed = 125\n<\/code><\/pre>\n\n\n\n
      and may generate:<\/p>\n\n\n\n
      Overspeed Alert\n<\/code><\/pre>\n\n\n\n
      Meanwhile another consumer stores the event.<\/p>\n\n\n\n
      Another consumer updates an analytics dashboard.<\/p>\n\n\n\n
      The producer does not need to directly call all three systems.<\/p>\n\n\n\n
      This is one of Kafka’s most important architectural benefits.<\/p>\n\n\n\n
      \n\n\n\n
      11. Kafka Is an Event Streaming Platform<\/h1>\n\n\n\n
      Now the definition should make more sense:<\/p>\n\n\n\n
      Event<\/h2>\n\n\n\n
      Something happened.<\/p>\n\n\n\n
      Vehicle changed speed.\n<\/code><\/pre>\n\n\n\n
      Streaming<\/h2>\n\n\n\n
      Events continuously arrive.<\/p>\n\n\n\n
      Event\nEvent\nEvent\nEvent\nEvent\n\u2192 continuously\n<\/code><\/pre>\n\n\n\n
      Distributed<\/h2>\n\n\n\n
      Kafka can run across multiple servers.<\/p>\n\n\n\n
      Broker 1\nBroker 2\nBroker 3\n<\/code><\/pre>\n\n\n\n
      Therefore:<\/p>\n\n\n\n
      Apache Kafka\n=\nDistributed\n+\nEvent\n+\nStreaming Platform\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      12. Kafka Is More Than Just Sending Messages<\/h1>\n\n\n\n
      A common beginner misunderstanding is:<\/p>\n\n\n\n
      \n
      Kafka simply sends a message from Application A to Application B.<\/p>\n<\/blockquote>\n\n\n\n
      Kafka can do much more.<\/p>\n\n\n\n
      Kafka can:<\/p>\n\n\n\n
      Receive events\nStore events\nOrganize events\nDistribute events\nReplicate events\nAllow multiple consumers\nAllow consumers to replay events\nHandle very large event streams\nScale across multiple servers\n<\/code><\/pre>\n\n\n\n
      A better mental model is:<\/p>\n\n\n\n
      Applications\n     \u2193\n     \u2193\n  PRODUCERS\n     \u2193\n+-------------------+\n|       KAFKA       |\n|                   |\n| Stores event      |\n| streams           |\n+-------------------+\n     \u2193\n  CONSUMERS\n     \u2193\nApplications\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      13. Kafka Stores Events<\/h1>\n\n\n\n
      Traditional messaging systems are often explained mainly as:<\/p>\n\n\n\n
      Send message\n     \u2193\nReceive message\n<\/code><\/pre>\n\n\n\n
      Kafka also keeps events for a configured amount of time.<\/p>\n\n\n\n
      Imagine:<\/p>\n\n\n\n
      Topic: vehicle-events\n\nOffset 0 \u2192 Event A\nOffset 1 \u2192 Event B\nOffset 2 \u2192 Event C\nOffset 3 \u2192 Event D\nOffset 4 \u2192 Event E\n<\/code><\/pre>\n\n\n\n
      A consumer could read:<\/p>\n\n\n\n
      A \u2192 B \u2192 C \u2192 D \u2192 E\n<\/code><\/pre>\n\n\n\n
      Later, depending on configuration and retained data, a consumer can read those events again.<\/p>\n\n\n\n
      This is called replaying events<\/strong>.<\/p>\n\n\n\n
      Replay is extremely important in real production systems.<\/p>\n\n\n\n
      We will study offsets and retention deeply later.<\/p>\n\n\n\n
      \n\n\n\n
      14. Kafka Is Not a Normal Database<\/h1>\n\n\n\n
      Kafka stores data, but Kafka should not automatically be treated as a replacement for systems such as:<\/p>\n\n\n\n
      PostgreSQL\nMySQL\nOracle\nMongoDB\n<\/code><\/pre>\n\n\n\n
      A database is usually designed for questions like:<\/p>\n\n\n\n
      Give me customer 101.\n\nFind all orders where amount > 1000.\n\nUpdate this customer's address.\n<\/code><\/pre>\n\n\n\n
      Kafka is designed around streams of ordered events.<\/p>\n\n\n\n
      For example:<\/p>\n\n\n\n
      OrderCreated\nOrderPaid\nOrderPacked\nOrderShipped\nOrderDelivered\n<\/code><\/pre>\n\n\n\n
      Many production architectures use both:<\/p>\n\n\n\n
      Application\n     \u2193\n   Kafka\n     \u2193\nDatabase\n<\/code><\/pre>\n\n\n\n
      Kafka and databases solve different problems.<\/p>\n\n\n\n
      \n\n\n\n
      15. Kafka Is Not Simply a REST API Replacement<\/h1>\n\n\n\n
      Suppose Service A needs an immediate response from Service B.<\/p>\n\n\n\n
      REST may be appropriate:<\/p>\n\n\n\n
      Service A\n    \u2193\nHTTP Request\n    \u2193\nService B\n    \u2193\nHTTP Response\n<\/code><\/pre>\n\n\n\n
      Kafka is excellent when the architecture is event-driven:<\/p>\n\n\n\n
      Service A\n    \u2193\nEvent\n    \u2193\nKafka\n    \u2193\nService B\nService C\nService D\n<\/code><\/pre>\n\n\n\n
      Real production systems commonly use:<\/p>\n\n\n\n
      REST + Kafka + Databases + Caches\n<\/code><\/pre>\n\n\n\n
      They complement each other.<\/p>\n\n\n\n
      \n\n\n\n
      16. Kafka in a Real Production Architecture<\/h1>\n\n\n\n
      A simplified production architecture could look like:<\/p>\n\n\n\n
                          PRODUCERS\n\nVehicles     Mobile Apps     Backend Services\n    \\             |               \/\n     \\            |              \/\n      +-----------+-------------+\n                  |\n                  v\n        +--------------------+\n        |   Kafka Cluster    |\n        |                    |\n        | Broker 1           |\n        | Broker 2           |\n        | Broker 3           |\n        +--------------------+\n                  |\n        +---------+---------+---------+\n        |         |         |         |\n        v         v         v         v\n\n   Analytics   Alerts   Database   Data Lake\n<\/code><\/pre>\n\n\n\n
      Notice an important design principle:<\/p>\n\n\n\n
      Producers do not need to know every consumer.<\/strong><\/p>\n\n\n\n
      That reduces coupling between applications.<\/p>\n\n\n\n
      \n\n\n\n
      17. Our Training Environment<\/h1>\n\n\n\n
      Throughout this Kafka Master Tutorials series, our practical learning environment will use a Confluent Kafka cluster<\/strong>.<\/p>\n\n\n\n
      Conceptually:<\/p>\n\n\n\n
      Our Application\n      \u2193\nKafka Producer\n      \u2193\nConfluent Kafka Cluster\n      \u2193\nKafka Consumer\n      \u2193\nOur Application\n<\/code><\/pre>\n\n\n\n
      We will gradually learn how to:<\/p>\n\n\n\n
      Create topics\nProduce events\nConsume events\nUse keys\nUnderstand partitions\nUnderstand offsets\nConfigure consumer groups\nConfigure reliability\nImplement security\nMonitor Kafka\nTroubleshoot Kafka\nDesign production architectures\n<\/code><\/pre>\n\n\n\n
      We will not jump directly into advanced configuration without first understanding why each feature exists.<\/p>\n\n\n\n
      \n\n\n\n
      18. Real-World Industries Using Kafka<\/h1>\n\n\n\n
      Kafka-style event streaming is useful in many industries.<\/p>\n\n\n\n
      Examples include:<\/p>\n\n\n\n
      Banking<\/h3>\n\n\n\n
      Transaction\n    \u2193\nKafka\n    \u2193\nFraud detection\nAnalytics\nNotifications\nAudit systems\n<\/code><\/pre>\n\n\n\n
      E-commerce<\/h3>\n\n\n\n
      Order\n   \u2193\nKafka\n   \u2193\nInventory\nPayment\nShipping\nAnalytics\n<\/code><\/pre>\n\n\n\n
      Telematics<\/h3>\n\n\n\n
      Vehicle\n   \u2193\nKafka\n   \u2193\nTracking\nAlerts\nTrips\nAnalytics\n<\/code><\/pre>\n\n\n\n
      IoT<\/h3>\n\n\n\n
      Sensors\n   \u2193\nKafka\n   \u2193\nMonitoring\nStorage\nAnalytics\n<\/code><\/pre>\n\n\n\n
      Websites<\/h3>\n\n\n\n
      User clicks\n    \u2193\nKafka\n    \u2193\nAnalytics\nRecommendations\nData warehouse\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      19. A Beginner Mental Model<\/h1>\n\n\n\n
      For now, remember Kafka using this picture:<\/p>\n\n\n\n
      Someone creates data\n        \u2193\n     PRODUCER\n        \u2193\n      TOPIC\n        \u2193\n      KAFKA\n        \u2193\n     CONSUMER\n        \u2193\nSomeone uses the data\n<\/code><\/pre>\n\n\n\n
      Example:<\/p>\n\n\n\n
      Vehicle\n   \u2193\nProducer\n   \u2193\nvehicle-events\n   \u2193\nKafka\n   \u2193\nConsumer\n   \u2193\nAnalytics\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      20. Production-Level Mental Model<\/h1>\n\n\n\n
      As you become more advanced, your mental model will grow into:<\/p>\n\n\n\n
                               Kafka Cluster\n\nProducer\n   |\n   v\n+------------------------------------------------+\n| Topic                                          |\n|                                                |\n| Partition 0 \u2192 Broker 1 \u2192 replicated elsewhere |\n| Partition 1 \u2192 Broker 2 \u2192 replicated elsewhere |\n| Partition 2 \u2192 Broker 3 \u2192 replicated elsewhere |\n+------------------------------------------------+\n        |                  |\n        |                  |\n        v                  v\n\nConsumer Group A      Consumer Group B\nAnalytics             Monitoring\n<\/code><\/pre>\n\n\n\n
      Eventually we will understand every component in this diagram.<\/p>\n\n\n\n
      That is how this series will take you from:<\/p>\n\n\n\n
      \"What is Kafka?\"\n<\/code><\/pre>\n\n\n\n
      to:<\/p>\n\n\n\n
      \"I can design and operate production-grade Kafka systems.\"\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      21. Common Beginner Mistakes<\/h1>\n\n\n\n
      Mistake 1<\/h3>\n\n\n\n
      Thinking Kafka is only a queue.<\/p>\n\n\n\n
      Kafka has queue-like capabilities, but the event log, retention, replay, partitioning, and multiple independent consumers make its model broader.<\/p>\n\n\n\n
      Mistake 2<\/h3>\n\n\n\n
      Thinking Kafka processes everything itself.<\/p>\n\n\n\n
      Kafka primarily stores and distributes event streams.<\/p>\n\n\n\n
      Applications or stream-processing systems perform business logic.<\/p>\n\n\n\n
      Mistake 3<\/h3>\n\n\n\n
      Thinking Kafka replaces every database.<\/p>\n\n\n\n
      It does not.<\/p>\n\n\n\n
      Mistake 4<\/h3>\n\n\n\n
      Thinking every application should use Kafka.<\/p>\n\n\n\n
      Kafka is powerful, but simple applications may not need event streaming.<\/p>\n\n\n\n
      Architecture should match the problem.<\/p>\n\n\n\n
      \n\n\n\n
      22. Interview-Level Question<\/h1>\n\n\n\n
      Question<\/h3>\n\n\n\n
      What is Apache Kafka?<\/p>\n\n\n\n
      Beginner Answer<\/h3>\n\n\n\n
      Apache Kafka is a system used to send and receive large amounts of data between applications.<\/p>\n\n\n\n
      Better Answer<\/h3>\n\n\n\n
      Apache Kafka is a distributed event streaming platform that allows producers to publish events to topics and consumers to read those events.<\/p>\n\n\n\n
      Production-Level Answer<\/h3>\n\n\n\n
      Apache Kafka is a distributed event streaming platform built around a durable, partitioned log. It enables scalable event ingestion, storage, distribution, replay, and asynchronous communication between independently scalable producers and consumers.<\/p>\n\n\n\n
      You do not need to memorize the production-level answer yet.<\/p>\n\n\n\n
      By the end of this series, you should understand every word in it.<\/p>\n\n\n\n
      \n\n\n\n
      23. Knowledge Check<\/h1>\n\n\n\n
      Try answering these without looking above:<\/p>\n\n\n\n
        \n
      1. What is an event?<\/li>\n\n\n\n
      2. What is event streaming?<\/li>\n\n\n\n
      3. What does a Kafka producer do?<\/li>\n\n\n\n
      4. What does a consumer do?<\/li>\n\n\n\n
      5. Where does Kafka store events?<\/li>\n\n\n\n
      6. What is a Kafka broker?<\/li>\n\n\n\n
      7. Can more than one application consume Kafka events?<\/li>\n\n\n\n
      8. Is Kafka the same as a relational database?<\/li>\n\n\n\n
      9. Why might replaying events be useful?<\/li>\n\n\n\n
      10. Why do production Kafka clusters normally contain multiple brokers?<\/li>\n<\/ol>\n\n\n\n
        \n\n\n\n
        24. Key Takeaways<\/h1>\n\n\n\n
        Remember these six points:<\/p>\n\n\n\n
        1. An EVENT represents something that happened.\n\n2. A PRODUCER sends events to Kafka.\n\n3. Kafka stores events in TOPICS.\n\n4. A CONSUMER reads events from Kafka.\n\n5. Multiple Kafka BROKERS can form a CLUSTER.\n\n6. Kafka enables scalable EVENT-DRIVEN systems.\n<\/code><\/pre>\n\n\n\n
        The most important architecture to remember from this first lesson is:<\/p>\n\n\n\n
        Producer\n   \u2193\nKafka Topic\n   \u2193\nConsumer\n<\/code><\/pre>\n\n\n\n
        Everything we learn later will build upon this simple model.<\/p>\n\n\n\n
        \n\n\n\n
        Next Tutorial<\/h2>\n\n\n\n
        Kafka Master Tutorials \u2014 02: Why Do We Need Kafka?<\/strong><\/p>\n\n\n\n
        In that tutorial, we will start with a system without Kafka<\/strong>, identify the problems, and then introduce Kafka step by step so that you understand why Kafka exists<\/em> instead of simply memorizing its features.<\/p>\n","protected":false},"excerpt":{"rendered":"
        What Is Apache Kafka? Learning Objective By the end of this tutorial, you should be able to explain: 1. Start With a Simple Problem Imagine that we… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1132","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/1132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=1132"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/1132\/revisions"}],"predecessor-version":[{"id":1138,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/1132\/revisions\/1138"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=1132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=1132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=1132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}