Event-driven architecture pattern in Spring Boot - Performance & Optimization

Performance: Event-driven architecture pattern

MEDIUM IMPACT

This pattern affects how quickly the application responds to user actions and external events, impacting interaction responsiveness and backend processing speed.

Handling user actions asynchronously in a Spring Boot app

Spring Boot

@Async
@EventListener
public void handleOrderCreated(OrderCreatedEvent event) {
  paymentService.charge(event.getOrder());
  inventoryService.updateStock(event.getOrder());
  notificationService.sendConfirmation(event.getOrder());
}

public void createOrder(Order order) {
  applicationEventPublisher.publishEvent(new OrderCreatedEvent(this, order));
}

Decouples processing by publishing events; handlers run asynchronously, improving responsiveness.

📈 Performance GainNon-blocking main thread; reduces INP by handling tasks in background.

Handling user actions asynchronously in a Spring Boot app

Spring Boot

public void processOrder(Order order) {
  // Direct synchronous processing
  paymentService.charge(order);
  inventoryService.updateStock(order);
  notificationService.sendConfirmation(order);
}

All services are called synchronously, blocking the main thread and increasing response time.

📉 Performance CostBlocks main thread until all steps complete, increasing INP and user wait time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous service calls	N/A	N/A	N/A	[X] Bad
Event-driven asynchronous handling	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Events are published and consumed asynchronously, reducing blocking in the main request thread and improving interaction responsiveness.

→Event Dispatch

→Thread Scheduling

→Backend Processing

⚠️ BottleneckEvent handling thread pool saturation can delay processing and increase latency.

Core Web Vital Affected

INP

This pattern affects how quickly the application responds to user actions and external events, impacting interaction responsiveness and backend processing speed.

Optimization Tips

1Avoid synchronous blocking calls in event handlers to keep UI responsive.

2Use efficient thread pools to prevent event processing delays.

3Decouple components to improve scalability and reduce latency.

Performance Quiz - 3 Questions

How does event-driven architecture improve user interaction responsiveness?

A By decoupling tasks and handling them asynchronously

B By running all tasks synchronously in the main thread

C By increasing the number of DOM nodes

D By blocking rendering until all events complete

DevTools: Performance

How to check: Record a performance profile during user interaction; look for long tasks blocking the main thread.

What to look for: Reduced long tasks and faster event handling indicate good event-driven performance.

Practice

1. What is the main purpose of the event-driven architecture pattern in Spring Boot?

easy

A. To store data in a relational database

B. To allow different parts of the application to communicate by sending and receiving events

C. To create user interfaces with HTML and CSS

D. To handle HTTP requests directly without any middleware

Solution

1. Step 1: Understand event-driven architecture basics

   This pattern lets components send and listen to events to communicate asynchronously.

2. Step 2: Identify Spring Boot usage

   Spring Boot uses Java classes and annotations to implement this pattern for flexible communication.

3. Final Answer:

   To allow different parts of the application to communicate by sending and receiving events -> Option B

4. Quick Check:

   Event-driven communication = To allow different parts of the application to communicate by sending and receiving events [OK]

Hint: Event-driven means parts talk by sending/listening events [OK]

Common Mistakes:

• Confusing event-driven with database storage
• Thinking it handles UI design
• Assuming it processes HTTP requests directly

2. Which annotation is used in Spring Boot to mark a method as an event listener?

easy

A. @EventHandler

B. @Listener

C. @HandleEvent

D. @EventListener

Solution

1. Step 1: Recall Spring Boot event listener annotation

   Spring Boot uses @EventListener to mark methods that listen for events.

2. Step 2: Check other options

   @EventHandler, @Listener, and @HandleEvent are not valid Spring Boot annotations for event listening.

3. Final Answer:

   @EventListener -> Option D

4. Quick Check:

   @EventListener marks event methods [OK]

Hint: Remember: @EventListener listens to events in Spring Boot [OK]

Common Mistakes:

• Using @EventHandler which is not a Spring Boot annotation
• Confusing with @Listener or @HandleEvent which don't exist
• Misspelling the annotation name

3. Given this Spring Boot event publishing code snippet, what will be printed?

public class MyEvent extends ApplicationEvent {
    public MyEvent(Object source) { super(source); }
}

@Component
public class Publisher {
    @Autowired
    private ApplicationEventPublisher publisher;

    public void publish() {
        publisher.publishEvent(new MyEvent(this));
    }
}

@Component
public class Listener {
    @EventListener
    public void onMyEvent(MyEvent event) {
        System.out.println("Event received");
    }
}

medium

A. Event received

B. No output

C. Compilation error

D. Runtime exception

Solution

1. Step 1: Understand event publishing

   The Publisher publishes a MyEvent instance using ApplicationEventPublisher.

2. Step 2: Understand event listening

   The Listener class has a method annotated with @EventListener that listens for MyEvent and prints "Event received".

3. Final Answer:

   Event received -> Option A

4. Quick Check:

   Publishing triggers listener print = Event received [OK]

Hint: Publishing event triggers listener print statement [OK]

Common Mistakes:

• Thinking no output because listener is missing
• Assuming compilation error due to event class
• Expecting runtime exception without error

4. What is wrong with this Spring Boot event listener code?

@Component
public class MyListener {
    @EventListener
    public void handleEvent(String event) {
        System.out.println("Event: " + event);
    }
}

medium

A. EventListener methods cannot accept String as event parameter

B. Missing @Component annotation

C. Method must return a value

D. EventListener annotation is misspelled

Solution

1. Step 1: Check event parameter type

   Spring events can be any object, including String, but using String as event parameter is discouraged because it may cause ambiguity and unintended triggers.

2. Step 2: Understand best practice

   Using custom event classes extending ApplicationEvent or plain objects is preferred for clarity and to avoid conflicts.

3. Final Answer:

   EventListener methods cannot accept String as event parameter -> Option A

4. Quick Check:

   String event param is invalid for event listener [OK]

Hint: EventListener needs custom event class, not String [OK]

Common Mistakes:

• Thinking @Component is missing
• Believing method must return a value
• Assuming annotation is misspelled

5. You want to build a Spring Boot app where multiple components react to a user registration event asynchronously. Which approach best fits the event-driven architecture pattern?

hard

A. Send HTTP requests manually between components

B. Call all components directly from the registration method without events

C. Create a UserRegisteredEvent class, publish it with ApplicationEventPublisher, and have multiple @EventListener methods handle it

D. Use a database trigger to notify components

Solution

1. Step 1: Identify event-driven pattern usage

   Creating a custom event class and publishing it allows decoupled communication between components.

2. Step 2: Understand asynchronous handling

   Multiple @EventListener methods can react independently and asynchronously to the event.

3. Step 3: Evaluate other options

   Direct calls, database triggers, or manual HTTP requests do not follow Spring Boot event-driven best practices.

4. Final Answer:

   Create a UserRegisteredEvent class, publish it with ApplicationEventPublisher, and have multiple @EventListener methods handle it -> Option C

5. Quick Check:

   Custom event + publisher + listeners = Create a UserRegisteredEvent class, publish it with ApplicationEventPublisher, and have multiple @EventListener methods handle it [OK]

Hint: Use custom event class and @EventListener for async reactions [OK]

Common Mistakes:

• Calling components directly, losing decoupling
• Relying on database triggers for app events
• Manually sending HTTP requests between components