0Pricing
SaaS Architecture & Startup Engineering · Lezione

Event Storming per i microservizi

Utilizzare Event Storming come tecnica collaborativa per individuare gli eventi di dominio e modellare processi aziendali complessi per il proprio SaaS.

Event Storming per i microservizi è una lezione SaaS Architecture & Startup Engineering 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 SaaS Architecture & Startup Engineering, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso SaaS Architecture & Startup Engineering include 4 lezioni in totale.

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

What is Event Storming?

Event Storming is a fun, collaborative workshop technique to understand complex business domains. It helps teams visualize how things happen in a system.

Imagine a room full of sticky notes! Teams map out a business process by focusing on the "events" that occur, making it easier to see the big picture.

Why Event Storm for Microservices?

For SaaS, especially with microservices, understanding domain boundaries is key. Event Storming helps:

  • Break down monoliths: Clearly identifies areas to split.
  • Define service boundaries: Groups related events and actions into potential services.
  • Improve communication: Gets everyone on the same page, from business to tech.

The Event Storming Canvas

Event Storming uses different colored sticky notes to represent various elements of your domain:

  • Orange: Domain Events (what happened?)
  • Blue: Commands (what triggers an event?)
  • Yellow: Aggregates (who performs a command?)
  • Green: Read Models (how users view data?)
  • Purple: Policies (rules reacting to events)

Step 1: Discovering Domain Events

This is the starting point! Think about "what happened?" in your business process. Events are facts from the past, always written in past tense.

Examples:

  • OrderPlaced
  • PaymentReceived
  • UserRegistered
  • SubscriptionCancelled

These are the core truths of your system.

Coding a Simple Event

While Event Storming is visual, the events we discover often translate into code. Here's how a simple OrderPlaced event might look in a Java application:

Try running this example to see how an event could be represented and "published" (here, just printed).

public class OrderPlacedEvent {
  private String orderId;
  private double amount;
  private String customerId;

  public OrderPlacedEvent(String orderId, double amount, String customerId) {
    this.orderId = orderId;
    this.amount = amount;
    this.customerId = customerId;
  }

  public String toString() {
    return "OrderPlacedEvent {id='" + orderId + "', amount=" + amount + ", customerId='" + customerId + "'}";
  }

  public static void main(String[] args) {
    OrderPlacedEvent event = new OrderPlacedEvent("ORD123", 99.99, "CUST456");
    System.out.println("New event generated: " + event.toString());
  }
}

Step 2: Identifying Commands

After events, we look for commands. A command is an explicit request to do something, which usually leads to an event (or multiple events).

Ask: "What action caused this event to happen?" Commands are usually imperative verbs.

  • PlaceOrder (leads to OrderPlaced)
  • ProcessPayment (leads to PaymentReceived)
  • RegisterUser (leads to UserRegistered)

Step 3: Pinpointing Aggregates

Aggregates are the "who" or "what" that receives a command and produces an event. They are transactional consistency boundaries – meaning everything within an aggregate changes together.

Think of them as the "model" or "entity" in your code that holds state and enforces business rules.

  • Order aggregate handles PlaceOrder.
  • PaymentProcessor handles ProcessPayment.

Step 4: Read Models & Policies

Read Models (Green): These are how users or other systems query information. They are optimized for reading, often denormalized views built from events.

Policies (Purple): These are business rules that react to events. For example, "when an OrderPlaced event occurs, then send a confirmation email."

From Storm to Bounded Contexts

As you map out your domain, you'll see natural clusters of events, commands, and aggregates. These clusters often define your Bounded Contexts.

A Bounded Context is a logical boundary within which a specific domain model is defined and applicable. This is crucial for designing independent microservices!

Benefits Beyond Design

Event Storming doesn't just help with technical design; it fosters a shared understanding across the entire team.

  • Shared Language: Everyone uses the same terms.
  • Knowledge Transfer: New team members quickly grasp complex flows.
  • Problem Identification: Uncovers hidden assumptions and issues early.

Quick Check

Event Storming uses different colored sticky notes to represent various domain elements. Match the sticky note color to its correct description.

Recap: Event Storming Toolkit

You've learned that Event Storming is a powerful, visual technique to understand complex domains. By focusing on Domain Events, you can identify Commands, Aggregates, Read Models, and Policies.

This collaborative approach helps in defining clear Bounded Contexts, making it an invaluable tool for designing robust and scalable microservices in your SaaS architecture.

Domande Frequenti

La lezione «Event Storming per i microservizi» è gratuita?

Sì — il testo completo di «Event Storming per i microservizi» è 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 SaaS Architecture & Startup Engineering, passa a CoddyKit PRO. Il corso SaaS Architecture & Startup Engineering include 4 lezioni in totale.

Cosa imparerò in «Event Storming per i microservizi»?

Utilizzare Event Storming come tecnica collaborativa per individuare gli eventi di dominio e modellare processi aziendali complessi per il proprio SaaS. Eserciti SaaS Architecture & Startup Engineering 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 SaaS Architecture & Startup Engineering?

Non è richiesta alcuna esperienza precedente. SaaS Architecture & Startup Engineering 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 Storming per i microservizi»?

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 SaaS Architecture & Startup Engineering?

Sì. Ogni lezione SaaS Architecture & Startup Engineering 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. Bounded Context e aggregati
  2. Event Storming per i microservizi
  3. Progettazione strategica e context mapping
  4. Linguaggio ubiquo e modello di dominio
← Torna a SaaS Architecture & Startup Engineering