0Pricing
SaaS Architecture & Startup Engineering · Aula

Tempestade de eventos para microsserviços

Utilize a tempestade de eventos como técnica colaborativa para descobrir eventos do domínio e modelar processos de negócios complexos para seu software como serviço.

Tempestade de eventos para microsserviços é uma aula grátis de SaaS Architecture & Startup Engineering no CoddyKit. Esta é a aula 2 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 SaaS Architecture & Startup Engineering, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de SaaS Architecture & Startup Engineering inclui 4 aulas no total.

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

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.

Perguntas Frequentes

A aula “Tempestade de eventos para microsserviços” é grátis?

Sim — o texto completo de “Tempestade de eventos para microsserviços” é 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 SaaS Architecture & Startup Engineering, atualize para CoddyKit PRO. O curso de SaaS Architecture & Startup Engineering inclui 4 aulas no total.

O que vou aprender em “Tempestade de eventos para microsserviços”?

Utilize a tempestade de eventos como técnica colaborativa para descobrir eventos do domínio e modelar processos de negócios complexos para seu software como serviço. Você pratica SaaS Architecture & Startup Engineering 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 SaaS Architecture & Startup Engineering?

Nenhuma experiência prévia é necessária. SaaS Architecture & Startup Engineering 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 2 de 4.

Quanto tempo leva a aula “Tempestade de eventos para microsserviços”?

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

Sim. Cada aula de SaaS Architecture & Startup Engineering 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. Contextos delimitados e agregados
  2. Tempestade de eventos para microsserviços
  3. Projeto estratégico e mapeamento de contextos
  4. Linguagem ubíqua e o modelo de domínio
← Voltar para SaaS Architecture & Startup Engineering