Apache Kafka & Stream Processing Fundamentals · Lezione

Join e aggregazioni nei flussi

Esegua join complessi tra flussi e tabelle e aggreghi i dati per ricavare informazioni utili in tempo reale.

Lezione 2 di 411 passaggi

Join e aggregazioni nei flussi è una lezione Apache Kafka & Stream Processing Fundamentals gratuita su CoddyKit. Questa è la lezione 2 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Apache Kafka & Stream Processing Fundamentals, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Apache Kafka & Stream Processing Fundamentals include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

Combining Data Streams

In real-world data processing, you often need to combine information from different sources. Imagine tracking user clicks and matching them with user profiles, or correlating an order with its payment details.

Kafka Streams provides powerful operations to join different data streams (KStreams) and tables (KTables) based on a common key. This allows you to enrich your data and derive more complete insights in real-time.

KStream-KStream Joins

A KStream-KStream join combines records from two KStreams based on their shared key. Since KStreams represent unbounded, continuous event streams, these joins require a time window.

  • Events from both streams must arrive within this defined time window to be considered for a join.
  • If an event from one stream arrives outside the window of its matching event in the other stream, they won't be joined.
  • This is crucial for correlating events that happen close together, like a user clicking an ad and then visiting a product page.

KStream-KStream Join Example

This example demonstrates joining two KStreams, streamA and streamB, using a 10-second time window. Only records with the same key arriving within this window will be combined.

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.kstream.JoinWindows;
import org.apache.kafka.streams.kstream.KStream;
import java.time.Duration;
import java.util.Properties;

public class StreamStreamJoin {
  public static void main(String[] args) {
    Properties props = new Properties();
    props.put(StreamsConfig.APPLICATION_ID_CONFIG, "stream-join-app");
    props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
    props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());
    props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());

    StreamsBuilder builder = new StreamsBuilder();
    KStream<String, String> streamA = builder.stream("topic-A");
    KStream<String, String> streamB = builder.stream("topic-B");

    KStream<String, String> joined = streamA.join(
        streamB,
        (valA, valB) -> "Joined: " + valA + "-" + valB,
        JoinWindows.of(Duration.ofSeconds(10))
    );
    joined.to("joined-topic");

    KafkaStreams streams = new KafkaStreams(builder.build(), props);
    streams.start();
  }
}

KStream-KTable Joins

A KStream-KTable join combines an event stream (KStream) with a materialized view or state table (KTable). This is a very common pattern for data enrichment.

  • When a new record arrives on the KStream, it's joined with the current state of the KTable for the matching key.
  • No time window is explicitly needed for the KTable side, as it always represents the latest known state.
  • Think of it as looking up additional details for an event from a constantly updating database.

KStream-KTable Join Example

Here, a stream of transactions is enriched with data from a user-profiles KTable. Each transaction record gets the latest profile information for its user.

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.kstream.KStream;
import org.apache.kafka.streams.kstream.KTable;
import java.util.Properties;

public class StreamTableJoin {
  public static void main(String[] args) {
    Properties props = new Properties();
    props.put(StreamsConfig.APPLICATION_ID_CONFIG, "stream-table-join-app");
    props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
    props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());
    props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());

    StreamsBuilder builder = new StreamsBuilder();
    KStream<String, String> transactions = builder.stream("transactions");
    KTable<String, String> userProfiles = builder.table("user-profiles");

    KStream<String, String> enrichedTransactions = transactions.join(
        userProfiles,
        (transactionVal, profileVal) -> "Tx: " + transactionVal + ", User: " + profileVal
    );
    enrichedTransactions.to("enriched-transactions");

    KafkaStreams streams = new KafkaStreams(builder.build(), props);
    streams.start();
  }
}

KTable-KTable Joins

A KTable-KTable join combines two materialized views (KTables) based on their shared key. This is similar to joining two constantly updating database tables.

  • Whenever a record in either KTable is updated, the join operation is re-evaluated for that key.
  • The output KTable will reflect the combined latest state of the matching records from both input KTables.
  • This is useful for combining different aspects of an entity, like product pricing and inventory levels.

KTable-KTable Join Example

This code joins product-prices and product-stocks KTables. Any update to a product's price or stock will trigger an update to the joined-products KTable.

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.kstream.KTable;
import java.util.Properties;

public class TableTableJoin {
  public static void main(String[] args) {
    Properties props = new Properties();
    props.put(StreamsConfig.APPLICATION_ID_CONFIG, "table-table-join-app");
    props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
    props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());
    props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());

    StreamsBuilder builder = new StreamsBuilder();
    KTable<String, String> productPrices = builder.table("product-prices");
    KTable<String, String> productStocks = builder.table("product-stocks");

    KTable<String, String> joinedProducts = productPrices.join(
        productStocks,
        (price, stock) -> "Price: " + price + ", Stock: " + stock
    );
    joinedProducts.toStream().to("joined-products");

    KafkaStreams streams = new KafkaStreams(builder.build(), props);
    streams.start();
  }
}

Understanding Aggregations

Aggregations are operations that summarize data from a stream or table over a specific key or time window. Common aggregations include:

  • Counting: How many events occurred for a key?
  • Summing: What is the total value for a key?
  • Averaging: What is the average value for a key?
  • Reducing: Combining values using a custom logic.

Aggregations are fundamental for building real-time dashboards, metrics, and summary statistics from continuous data streams.

KStream Aggregation Example

This example demonstrates a simple aggregation: counting user events per user ID within 10-second tumbling windows. The groupByKey() and windowedBy() methods are key here.

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.kstream.KStream;
import org.apache.kafka.streams.kstream.Materialized;
import org.apache.kafka.streams.kstream.TimeWindows;
import java.time.Duration;
import java.util.Properties;

public class StreamAggregation {
  public static void main(String[] args) {
    Properties props = new Properties();
    props.put(StreamsConfig.APPLICATION_ID_CONFIG, "stream-aggregation-app");
    props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
    props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());
    props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CONFIG, Serdes.String().getClass());

    StreamsBuilder builder = new StreamsBuilder();
    KStream<String, String> userEvents = builder.stream("user-events");

    userEvents
        .groupByKey()
        .windowedBy(TimeWindows.of(Duration.ofSeconds(10)))
        .count(Materialized.as("user-event-counts"))
        .toStream((windowedKey, count) -> windowedKey.key())
        .to("user-event-counts-output");

    KafkaStreams streams = new KafkaStreams(builder.build(), props);
    streams.start();
  }
}

Join & Aggregate Check

Which type of Kafka Streams join is typically used for data enrichment, where an incoming event stream is combined with the latest state of a dataset?

Joins & Aggregations Summary

You've learned how Kafka Streams allows you to combine and summarize data in powerful ways:

  • KStream-KStream Joins: Correlate events from two streams within a time window.
  • KStream-KTable Joins: Enrich stream events with the latest state from a table.
  • KTable-KTable Joins: Combine two continuously updating materialized views.
  • Aggregations: Summarize data (e.g., count, sum) over keys and windows to derive real-time insights.

These operations are key to building sophisticated real-time analytics and data processing pipelines with Kafka Streams.

Gratis per iniziare

Impara Apache Kafka & Stream Processing Fundamentals con un tutor IA — gratis

Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.

Corsi
12
Lezioni
48

Domande Frequenti

La lezione «Join e aggregazioni nei flussi» è gratuita?

Sì — il testo completo di «Join e aggregazioni nei flussi» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Apache Kafka & Stream Processing Fundamentals, passa a CoddyKit PRO. Il corso Apache Kafka & Stream Processing Fundamentals include 4 lezioni in totale.

Cosa imparerò in «Join e aggregazioni nei flussi»?

Esegua join complessi tra flussi e tabelle e aggreghi i dati per ricavare informazioni utili in tempo reale. Eserciti Apache Kafka & Stream Processing Fundamentals con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Apache Kafka & Stream Processing Fundamentals?

Non è richiesta alcuna esperienza precedente. Apache Kafka & Stream Processing Fundamentals su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 2 di 4.

Quanto tempo richiede la lezione «Join e aggregazioni nei flussi»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Apache Kafka & Stream Processing Fundamentals?

Sì. Ogni lezione Apache Kafka & Stream Processing Fundamentals include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Operazioni di windowing in Kafka Streams
  2. Join e aggregazioni nei flussi
  3. Introduzione a KSQL per l'analisi dei flussi
  4. Query interattive e state store
← Torna a Apache Kafka & Stream Processing Fundamentals