Event bus e broker di messaggi
Utilizzi broker di messaggi ed event bus per facilitare una comunicazione asincrona affidabile nelle choreography saga.
Event bus e broker di messaggi è una lezione Microservices Communication Patterns (Saga, Circuit Breaker) 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 Microservices Communication Patterns (Saga, Circuit Breaker), e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Microservices Communication Patterns (Saga, Circuit Breaker) include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Reliable Choreography Sagas
In a choreography saga, services communicate by exchanging events. For this to work reliably in a distributed system, we need robust communication mechanisms.
Imagine an order being created, then needing payment, and finally shipping. Each step is an event triggering the next service.
- Order Service publishes
OrderCreated - Payment Service subscribes to
OrderCreated, publishesPaymentProcessed - Shipping Service subscribes to
PaymentProcessed, publishesShipmentScheduled
What's an Event Bus?
An Event Bus is a pattern that enables different parts of an application (or different services) to communicate by sending and receiving events without knowing about each other directly.
Think of it as a central hub where events are broadcast. Any interested party can 'listen' for specific events.
It decouples services, meaning they don't need to know who will process their events, only that an event occurred.
Event Bus in Action
Consider an internal event bus within a single application:
- A user clicks a 'Save' button.
- The UI component publishes a
UserSavedevent to the event bus. - A logging module, a notification module, and a data synchronization module might all subscribe to
UserSaved.
They all react to the event without the UI knowing about them. This is simple and effective for in-process communication.
Introducing Message Brokers
While an event bus is great for in-process communication, distributed microservices need more. This is where Message Brokers come in.
A message broker is a dedicated service (like RabbitMQ, Kafka, or AWS SQS) that acts as an intermediary for messages between different applications or services.
It provides advanced features essential for reliable communication across networks.
Broker Benefits for Sagas
Message brokers offer crucial benefits for choreography sagas:
- Durability: Messages persist even if services are down, preventing data loss.
- Guaranteed Delivery: Ensures messages reach their intended consumers.
- Decoupling: Senders and receivers don't know each other, promoting service independence.
- Load Balancing: Distributes messages efficiently among multiple instances of a consuming service.
- Asynchronous: Services don't wait for responses, improving performance and responsiveness.
Bus vs. Broker: The Difference
While both facilitate event-driven communication, an Event Bus is typically a lightweight, in-memory mechanism within a single application or process.
A Message Broker is a robust, external system designed for inter-process and inter-service communication across a network. It provides features like message queues, topics, persistence, and complex routing.
You can think of a message broker as a powerful, distributed implementation of an event bus concept.
Brokers Enable Choreography
Message brokers are the backbone of choreography sagas. They allow services to:
- Publish Events: A service completes a step and publishes an event to a specific topic (a named channel on the broker).
- Subscribe to Events: Other services interested in that event subscribe to the topic and receive the event to trigger their next step.
This decentralized flow, driven by events through a broker, defines the choreography pattern.
Example: Publishing an Event
Here's a simplified example of how an OrderService might prepare and conceptually "publish" an OrderCreated event using a message broker.
The broker handles the actual sending to subscribers.
public class OrderService {
public static void main(String[] args) {
String orderId = "ORD_456";
String customer = "Alice";
String item = "Widget";
// Imagine this event goes to a message broker
String eventPayload = "{ \"type\": \"OrderCreated\", \"orderId\": \"" + orderId + "\", \"customer\": \"" + customer + "\", \"item\": \"" + item + "\" }";
System.out.println("OrderService prepares event:");
System.out.println(eventPayload);
System.out.println("This event would be sent to a 'order_events' topic on a message broker.");
}
}Example: Subscribing to an Event
Now, let's see how a PaymentService would conceptually "subscribe" to and process the OrderCreated event from the broker.
It listens on the order_events topic.
public class PaymentService {
public static void main(String[] args) {
// Imagine PaymentService receives this event from a message broker
String receivedEvent = "{ \"type\": \"OrderCreated\", \"orderId\": \"ORD_456\", \"customer\": \"Alice\", \"item\": \"Widget\" }";
System.out.println("PaymentService received event:");
System.out.println(receivedEvent);
// Parse and process the event
if (receivedEvent.contains("\"type\": \"OrderCreated\"")) {
System.out.println("Processing payment for order: ORD_456...");
System.out.println("Payment processed successfully!");
} else {
System.out.println("Unknown event type received.");
}
}
}Check Your Understanding
Message brokers are crucial for choreography sagas. Which of the following are key benefits provided by message brokers for reliable asynchronous communication?
Recap: Event Bus & Brokers
In this lesson, we explored how Event Buses and Message Brokers facilitate reliable asynchronous communication, especially for choreography sagas.
- An Event Bus is a pattern for in-process event communication.
- A Message Broker is an external, robust system that implements this pattern for distributed services, offering features like durability and guaranteed delivery.
- They enable services to publish events and subscribe to topics, forming the core of how choreography sagas progress.
Next, we'll look at how to handle compensation when things go wrong in these event-driven flows!
Impara Microservices Communication Patterns (Saga, Circuit Breaker) 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 «Event bus e broker di messaggi» è gratuita?
Sì — il testo completo di «Event bus e broker di messaggi» è 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 Microservices Communication Patterns (Saga, Circuit Breaker), passa a CoddyKit PRO. Il corso Microservices Communication Patterns (Saga, Circuit Breaker) include 4 lezioni in totale.
Cosa imparerò in «Event bus e broker di messaggi»?
Utilizzi broker di messaggi ed event bus per facilitare una comunicazione asincrona affidabile nelle choreography saga. Eserciti Microservices Communication Patterns (Saga, Circuit Breaker) 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 Microservices Communication Patterns (Saga, Circuit Breaker)?
Non è richiesta alcuna esperienza precedente. Microservices Communication Patterns (Saga, Circuit Breaker) 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 «Event bus e broker di messaggi»?
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 Microservices Communication Patterns (Saga, Circuit Breaker)?
Sì. Ogni lezione Microservices Communication Patterns (Saga, Circuit Breaker) 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
- Progettazione di Saga basate sugli eventi
- Event bus e broker di messaggi
- Gestione delle compensazioni con gli eventi
- Creare consumer di eventi idempotenti