<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Event Sourcing on YennJ12 Engineering Blog</title><link>https://yennj12.js.org/yennj12_blog_V4/tags/event-sourcing/</link><description>Recent content in Event Sourcing on YennJ12 Engineering Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 28 Jan 2025 01:00:00 +0800</lastBuildDate><atom:link href="https://yennj12.js.org/yennj12_blog_V4/tags/event-sourcing/feed.xml" rel="self" type="application/rss+xml"/><item><title>SAGA Pattern: Managing Distributed Transactions in Spring Boot Microservices</title><link>https://yennj12.js.org/yennj12_blog_V4/posts/saga-pattern-distributed-transactions-spring-boot/</link><pubDate>Tue, 28 Jan 2025 01:00:00 +0800</pubDate><guid>https://yennj12.js.org/yennj12_blog_V4/posts/saga-pattern-distributed-transactions-spring-boot/</guid><description>🎯 Introduction In the era of microservices architecture, managing transactions across multiple services presents significant challenges. Traditional distributed transaction mechanisms like Two-Phase Commit (2PC) often lead to tight coupling, reduced availability, and poor performance. The SAGA Pattern emerges as a powerful alternative, providing a way to manage distributed transactions through a sequence of local transactions, each with compensating actions for rollback scenarios.
📚 What is the SAGA Pattern? 🔍 Core Concepts The SAGA pattern is a design pattern for managing long-running distributed transactions across multiple microservices.</description></item></channel></rss>