0Pricing
Apache Kafka & Stream Processing Fundamentals · Aula

Operações sem estado versus com estado

Entenda como o Kafka Streams processa dados com ou sem a manutenção de estado interno entre os registros.

Operações sem estado versus com estado é uma aula grátis de Apache Kafka & Stream Processing Fundamentals no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Apache Kafka & Stream Processing Fundamentals, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Apache Kafka & Stream Processing Fundamentals inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Stateless vs. Stateful Streams

In Kafka Streams, how you process data falls into two main categories: stateless and stateful operations.

Understanding this distinction is crucial for building efficient and correct real-time data pipelines. It impacts how your application remembers (or forgets) past events.

What are Stateless Operations?

Stateless operations process each incoming record independently. They don't remember any past records or maintain an internal state across events.

Think of it like a simple function: you give it an input, and it produces an output, without needing any memory of previous inputs.

Stateless Example: Map & Filter

Common stateless operations include map, filter, flatMap, and peek. They transform or filter records one by one.

Here's a simple Kafka Streams app using mapValues to convert all incoming message values to uppercase:

import org.apache.kafka.common.serialization.Serdes;
import org.apache.kafka.streams.KafkaStreams;
import org.apache.kafka.streams.StreamsBuilder;
import org.apache.kafka.streams.StreamsConfig;
import org.apache.kafka.streams.Topology;
import org.apache.kafka.streams.kstream.KStream;

import java.util.Properties;

public class StatelessMapApp {
  public static void main(String[] args) {
    Properties props = new Properties();
    props.put(StreamsConfig.APPLICATION_ID_CONFIG,
              "stateless-map-app");
    props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG,
              "localhost:9092");
    props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CLASS_CONFIG,
              Serdes.String().getClass());
    props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CLASS_CONFIG,
              Serdes.String().getClass());

    StreamsBuilder builder = new StreamsBuilder();
    KStream<String, String> source = builder.stream("input-topic");

    // Stateless operation: mapValues
    KStream<String, String> upperCaseStream =
        source.mapValues(value -> value.toUpperCase());

    upperCaseStream.to("output-topic");

    Topology topology = builder.build();
    KafkaStreams streams = new KafkaStreams(topology, props);
    streams.start();
    // In a real app, add a shutdown hook.
  }
}

When to Use Stateless Operations

Stateless operations are ideal for:

  • Simple Transformations: Changing data format, type conversion.
  • Filtering: Removing unwanted records.
  • Data Cleansing: Basic sanitization of individual records.

They are generally simpler to implement and have less overhead because no state needs to be managed.

What are Stateful Operations?

Stateful operations are those that need to remember past records or combine information across multiple records to produce a result.

They maintain an internal state, which is stored locally within the Kafka Streams application instance. This state allows them to perform aggregations, joins, and windowing.

Stateful Example: Counting Events

A classic example of a stateful operation is count(). To count events per key, the application must remember previous counts for each key.

This operation transforms a KStream into a KTable, which represents a changelog of aggregated results.

import org.apache.kafka.common.serialization.Serdes;
import org.apache.kafka.streams.KafkaStreams;
import org.apache.kafka.streams.StreamsBuilder;
import org.apache.kafka.streams.StreamsConfig;
import org.apache.kafka.streams.Topology;
import org.apache.kafka.streams.kstream.KStream;
import org.apache.kafka.streams.kstream.KTable;
import org.apache.kafka.streams.kstream.Materialized;

import java.util.Properties;

public class StatefulCountApp {
  public static void main(String[] args) {
    Properties props = new Properties();
    props.put(StreamsConfig.APPLICATION_ID_CONFIG,
              "stateful-count-app");
    props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG,
              "localhost:9092");
    props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CLASS_CONFIG,
              Serdes.String().getClass());
    props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CLASS_CONFIG,
              Serdes.String().getClass());

    StreamsBuilder builder = new StreamsBuilder();
    KStream<String, String> source = builder.stream("input-topic");

    // Stateful operation: count by key
    KTable<String, Long> countsTable = source
        .groupByKey()
        .count(Materialized.as("counts-store")); // A named state store

    countsTable.toStream().to("output-topic");

    Topology topology = builder.build();
    KafkaStreams streams = new KafkaStreams(topology, props);
    streams.start();
    // In a real app, add a shutdown hook.
  }
}

More Stateful Operations

Besides count(), other common stateful operations include:

  • Aggregations: reduce(), aggregate() (e.g., calculating sums, averages).
  • Joins: Combining data from two streams or a stream and a table based on a common key.
  • Windowing: Grouping records that fall within a defined time frame (e.g., 5-minute window).

These operations all rely on maintaining state to function correctly.

Kafka Streams State Stores

Kafka Streams manages state using internal state stores. These are typically backed by a local key-value store like RocksDB.

For fault tolerance, Kafka Streams also uses internal Kafka topics (called changelog topics) to continuously back up the state store. If an application instance fails, its state can be restored from the changelog topic by a new instance.

Quick Check: Identify Operations

Which of these Kafka Streams operations is considered stateless?

Recap: Stateless vs. Stateful

We've explored the key differences between stateless and stateful operations in Kafka Streams:

  • Stateless: Processes records individually, no memory of past events. Ideal for simple transformations and filtering.
  • Stateful: Requires internal memory (state stores) to combine or remember information across records. Essential for aggregations, joins, and windowing.

Choosing the right type of operation is fundamental to designing robust and efficient stream processing applications.

Perguntas Frequentes

A aula “Operações sem estado versus com estado” é grátis?

Sim — o texto completo de “Operações sem estado versus com estado” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Apache Kafka & Stream Processing Fundamentals, atualize para CoddyKit PRO. O curso de Apache Kafka & Stream Processing Fundamentals inclui 4 aulas no total.

O que vou aprender em “Operações sem estado versus com estado”?

Entenda como o Kafka Streams processa dados com ou sem a manutenção de estado interno entre os registros. Você pratica Apache Kafka & Stream Processing Fundamentals com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Apache Kafka & Stream Processing Fundamentals?

Nenhuma experiência prévia é necessária. Apache Kafka & Stream Processing Fundamentals no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.

Quanto tempo leva a aula “Operações sem estado versus com estado”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Apache Kafka & Stream Processing Fundamentals?

Sim. Cada aula de Apache Kafka & Stream Processing Fundamentals inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Construindo uma aplicação simples com Kafka Streams
  2. Conceitos de KStream e KTable
  3. Operações sem estado versus com estado
  4. Serdes e serialização de dados no Kafka Streams
← Voltar para Apache Kafka & Stream Processing Fundamentals