36/getting-started/index.xml - kafka-site - Git at Google

 <?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on Apache Kafka</title><link>https://kafka.apache.org/36/getting-started/</link><description>Recent content in Getting Started on Apache Kafka</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://kafka.apache.org/36/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction</title><link>https://kafka.apache.org/36/getting-started/introduction/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/introduction/</guid><description>What is event streaming? Event streaming is the digital equivalent of the human body&amp;rsquo;s central nervous system. It is the technological foundation for the &amp;lsquo;always-on&amp;rsquo; world where businesses are increasingly software-defined and automated, and where the user of software is more software.
 Technically speaking, event streaming is the practice of capturing data in real-time from event sources like databases, sensors, mobile devices, cloud services, and software applications in the form of streams of events; storing these event streams durably for later retrieval; manipulating, processing, and reacting to the event streams in real-time as well as retrospectively; and routing the event streams to different destination technologies as needed.</description></item><item><title>Use Cases</title><link>https://kafka.apache.org/36/getting-started/uses/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/uses/</guid><description>Here is a description of a few of the popular use cases for Apache Kafka®. For an overview of a number of these areas in action, see this blog post.
 Messaging Kafka works well as a replacement for a more traditional message broker. Message brokers are used for a variety of reasons (to decouple processing from data producers, to buffer unprocessed messages, etc). In comparison to most messaging systems Kafka has better throughput, built-in partitioning, replication, and fault-tolerance which makes it a good solution for large scale message processing applications.</description></item><item><title>Quick Start</title><link>https://kafka.apache.org/36/getting-started/quickstart/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/quickstart/</guid><description>Step 1: Get Kafka Download the latest Kafka release and extract it:
 $ tar -xzf kafka_2.13-3.6.2.tgz $ cd kafka_2.13-3.6.2 Step 2: Start the Kafka environment NOTE: Your local environment must have Java 8+ installed.
 Apache Kafka can be started using ZooKeeper or KRaft. To get started with either configuration follow one the sections below but not both.
 Kafka with ZooKeeper Run the following commands in order to start all services in the correct order:</description></item><item><title>Ecosystem</title><link>https://kafka.apache.org/36/getting-started/ecosystem/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/ecosystem/</guid><description>There are a plethora of tools that integrate with Kafka outside the main distribution. The ecosystem page lists many of these, including stream processing systems, Hadoop integration, monitoring, and deployment tools.</description></item><item><title>Upgrading</title><link>https://kafka.apache.org/36/getting-started/upgrade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/upgrade/</guid><description>Upgrading to 3.6.2 from any version 0.8.x through 3.5.x Upgrading ZooKeeper-based clusters If you are upgrading from a version prior to 2.1.x, please see the note in step 5 below about the change to the schema used to store consumer offsets. Once you have changed the inter.broker.protocol.version to the latest version, it will not be possible to downgrade to a version prior to 2.1.
 For a rolling upgrade:
 Update server.</description></item></channel></rss>
	<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on Apache Kafka</title><link>https://kafka.apache.org/36/getting-started/</link><description>Recent content in Getting Started on Apache Kafka</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://kafka.apache.org/36/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction</title><link>https://kafka.apache.org/36/getting-started/introduction/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/introduction/</guid><description>What is event streaming? Event streaming is the digital equivalent of the human body&rsquo;s central nervous system. It is the technological foundation for the &lsquo;always-on&rsquo; world where businesses are increasingly software-defined and automated, and where the user of software is more software.
	Technically speaking, event streaming is the practice of capturing data in real-time from event sources like databases, sensors, mobile devices, cloud services, and software applications in the form of streams of events; storing these event streams durably for later retrieval; manipulating, processing, and reacting to the event streams in real-time as well as retrospectively; and routing the event streams to different destination technologies as needed.</description></item><item><title>Use Cases</title><link>https://kafka.apache.org/36/getting-started/uses/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/uses/</guid><description>Here is a description of a few of the popular use cases for Apache Kafka®. For an overview of a number of these areas in action, see this blog post.
	Messaging Kafka works well as a replacement for a more traditional message broker. Message brokers are used for a variety of reasons (to decouple processing from data producers, to buffer unprocessed messages, etc). In comparison to most messaging systems Kafka has better throughput, built-in partitioning, replication, and fault-tolerance which makes it a good solution for large scale message processing applications.</description></item><item><title>Quick Start</title><link>https://kafka.apache.org/36/getting-started/quickstart/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/quickstart/</guid><description>Step 1: Get Kafka Download the latest Kafka release and extract it:
	$ tar -xzf kafka_2.13-3.6.2.tgz $ cd kafka_2.13-3.6.2 Step 2: Start the Kafka environment NOTE: Your local environment must have Java 8+ installed.
	Apache Kafka can be started using ZooKeeper or KRaft. To get started with either configuration follow one the sections below but not both.
	Kafka with ZooKeeper Run the following commands in order to start all services in the correct order:</description></item><item><title>Ecosystem</title><link>https://kafka.apache.org/36/getting-started/ecosystem/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/ecosystem/</guid><description>There are a plethora of tools that integrate with Kafka outside the main distribution. The ecosystem page lists many of these, including stream processing systems, Hadoop integration, monitoring, and deployment tools.</description></item><item><title>Upgrading</title><link>https://kafka.apache.org/36/getting-started/upgrade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/36/getting-started/upgrade/</guid><description>Upgrading to 3.6.2 from any version 0.8.x through 3.5.x Upgrading ZooKeeper-based clusters If you are upgrading from a version prior to 2.1.x, please see the note in step 5 below about the change to the schema used to store consumer offsets. Once you have changed the inter.broker.protocol.version to the latest version, it will not be possible to downgrade to a version prior to 2.1.
	For a rolling upgrade:
	Update server.</description></item></channel></rss>