Define async processing patterns with @Async, Virtual Threads, and @TransactionalEventListener.
npx skills add https://github.com/gykk16/spring-skeleton --skill async-event
Please help me install this Agent Skill. Skill: async-event Source: https://github.com/gykk16/spring-skeleton/tree/main/.omc/skills/async-event Command: npx skills add https://github.com/gykk16/spring-skeleton --skill async-event
This Skill provides clear rules and best practices for implementing asynchronous operations and event-driven communication within Spring applications, ensuring robust, scalable, and maintainable code.
@Async with Virtual Threads for non-blocking operations.@TransactionalEventListener to trigger side effects reliably after transaction commits.Use the async-event skill to configure asynchronous processing for a new order creation event.
High-intent search queries and answers about installing and using this skill.
To trigger side effects after a Spring transaction commits, use `@TransactionalEventListener` combined with `@Async`. This ensures actions like sending emails execute reliably only after the database transaction succeeds.
Propagating MDC context across async virtual threads in Spring requires explicit context passing within the `@Async` execution. This ensures trace IDs are preserved for request traceability in asynchronous event-driven processing.
A transactional event listener might execute before the database commit due to incorrect event listener phasing. You must configure the listener to run specifically in the `AFTER_COMMIT` phase to avoid this pitfall.
The best way to handle external I/O within Spring database transactions is to extract it using event-driven design. Move the I/O operations to an `@Async` method triggered after the transaction commits.
Yes, you can use `@Async` with virtual threads in Spring for non-blocking operations. This combination handles side effects concurrently without blocking the main user request thread.
Limitations of `@TransactionalEventListener` for async processing include potential MDC context loss and incorrect execution phasing if not explicitly configured. It also requires careful handling to avoid external I/O within the transaction.
rizaldiemImplement event-driven communication in Spring Boot with domain events and Kafka.
itallstartedwithaideaImplement structured logging, distributed tracing, and error monitoring for Cloudflare Workers.
PillArmyManage database sessions and transactions in Spring Boot applications.
delorenjDesign event-driven architectures with Kafka, RabbitMQ, and SQS/SNS.