- Published on
Deep dive into decoupling core domain logic from secondary concerns using @TransactionalEventListener, @Async, and Spring Retry mechanisms for resilient backend architectures.
Transaction
All Posts
- spring-boot (20)
- backend-architecture (19)
- microservices (15)
- java-25 (13)
- kafka (9)
- postgresql (8)
- spring-boot-40 (7)
- apache-kafka (6)
- jpa (5)
- java (4)
- performance (4)
- distributed-systems (3)
- event-driven (3)
- cqrs (3)
- concurrency (3)
- event-driven-architecture (3)
- virtual-threads (2)
- resilience (2)
- redis (2)
- async (2)
- transactional-outbox (1)
- idempotency (1)
- observability (1)
- distributed-tracing (1)
- opentelemetry (1)
- eventsourcing (1)
- distributed-transactions (1)
- saga-pattern (1)
- resilience4j (1)
- caching (1)
- caffeine (1)
- rate-limiting (1)
- api-security (1)
- kafka-streams (1)
- materialized-views (1)
- event-sourcing (1)
- optimistic-locking (1)
- batch-processing (1)
- structured-concurrency (1)
- schema-evolution (1)
- avro (1)
- event-driven-systems (1)
- debezium (1)
- cdc (1)
- data-projections (1)
- read-models (1)
- graalvm (1)
- native-image (1)
- aot (1)
- docker (1)
- microservice-security (1)
- oauth-21 (1)
- oidc (1)
- spring-security-6x (1)
- jwt (1)
- fault-tolerance (1)
- database-sharding (1)
- data-partitioning (1)
- scalability (1)
- reactive-programming (1)
- spring-webflux (1)
- project-reactor (1)
- r2dbc (1)
- non-blocking-io (1)
- microservices-performance (1)
- grpc (1)
- java-virtual-threads (1)
- protobuf (1)
- rpc (1)
- high-performance (1)
- java-concurrency (1)
- thread-pool (1)
- performance-tuning (1)
- spring-event (1)
- transaction (1)