A different flavor of the distributed transaction

on YouTube ↗53m

" summary

Demonstrates a MicroProfile spec called Long Running Actions (LRA) that implements the saga pattern for non-blocking distributed transactions in Java microservices, using Narayana (and mentions Payara) with Quarkus, JAX‑RS and REST clients. Shows two services that propagate an LRA ID, invoke operations, and on failure trigger compensating endpoints; compensation and completion callbacks work in the demo, recovery retries are issued by the coordinator until a decision, and a manual start/close flow is implemented and exercised.

AI-written summary · about

" chapters (17)

1. 0:00Introduction
2. 1:43Asset Transaction
3. 2:30Consensus Protocols
4. 7:07Saga
5. 9:19Saga Example
6. 12:42Availability vs Consistency
7. 14:41Centralization and Orchestration
8. 15:32Profile Specification
9. 16:14Rest invocation
10. 21:01Starting the project
11. 39:28Restriction
12. 39:43REST Client
13. 43:33Service Propagation
14. 45:38AfterLarray
15. 47:23Built
16. 47:53Not closing
17. 50:13Conclusion

" related talks

• 31mAddressing the transaction challenge in a cloud-native worldGrace Jansen · EclipseCon 2022
• 50mTransactional solutions for microservicesOndra Chaloupka, Adam Růžička · DevConf.CZ 2019
• 46mAddressing the transaction challenge in a cloud-native worldGrace Jansen · Devoxx Ukraine 2022: Secure our Future
• 41mTransactions in Your Micro-Services ArchitectureRudy De Busscher · Voxxed Days Microservices 2019
• 47mMicroservices Architecture and Data Consistency: So How Do We Do It for Real?JF James · Devoxx France 2022
• 55mTackling transactions in Microservices applicationsRubén Pérez · Software Craftsmanship Barcelona 2017
• 17mSaga Pattern for Distributed TransactionsDmitry Khorev · Conf42 Cloud Native 2023
• 46mLost in transaction? Strategies to deal with (in-)consistency in distributed systemsBernd Rücker · Full Stack Fest 2018