Transactions in Microservices
2 likes769 views
This document discusses transactions in microservices architectures and introduces MicroProfile Long Running Actions (LRA) as a solution. It provides an overview of LRA components and flow, and key concepts like compensation and timeouts. Code examples demonstrate using LRA annotations to define long-running transactions across multiple services.
Ad
More Related Content
What's hot (19)
Similar to Transactions in Microservices (20)
Ad
More from Payara (20)
![Rapid development tools for java ee 8 and micro profile [GIDS]](https://cdn.slidesharecdn.com/ss_thumbnails/rapiddevelopmenttoolsforjavaee8andmicroprofilegids1-180517150237-thumbnail.jpg?width=560&fit=bounds)
Ad
Recently uploaded (20)
Transactions in Microservices
- 1. #voxxed_lu Transactions in your micro- services architecture Dawn Parzych (CatchPoint)
- 2. #voxxed_lu What ? • Transaction and Micro-Services • MicroProfile LRA (Long Running Actions) • Demo
- 3. Rudy De Busscher • Payara • Service team • Involved in • Java EE Security API Expert group member • Committer in Eclipse EE4J groups • Committer of MicroProfile @rdebusscher https://blog.payara.fish/ https://www.atbash.be
- 4. #voxxed_lu Transaction • Typical concept from the ‘Monolith’ • Start - End • Typical short - to avoid locks • Multiple datasources supported with XA transactions
- 5. #voxxed_lu Transaction • Distributed - XA transactions • 2 Phase Commit • Not scalable • Locks DZone - XA transactions fizalihsan - Transactions
- 6. #voxxed_lu To be ACID or Not • Atomicity: All or Nothing • Consistency: All values are aligned • Isolation: Different transactions can’t see ‘temporal’ values • Durable: Reliably Stored • CAP Theorem • Consistency - Availability - Partitioning
- 7. #voxxed_lu Long Running Transactions • Multiple Datasource • Several actions over long period • Single Unit of Work? Web Services Journal
- 8. #voxxed_lu Example • Book Flight • Book Hotel • Payment AltexSoft
- 9. #voxxed_lu MicroService world • No Atomicity • Eventual Consistency • No Isolation • Durable KumuluzEE
- 11. #voxxed_lu • Optimizing Enterprise Java for a Micro-services Architecture • Based on some Java EE (Jakarta EE) specs
- 12. #voxxed_lu • API not stable yet • General Ideas defined
- 13. #voxxed_lu MicroProfile LRA • Long Running Actions • Features • Loose coupling • Guaranteed a globally consistent outcome • Compensatable actions (SAGAs)
- 14. #voxxed_lu LRA Components JAX-RS resource JAX-RS resource JAX-RS resource Coordinator Participant Participant Participant Callback Enlist
- 15. #voxxed_lu Typical Flow Start LRA Close LRA Enlist Participant1 Coordinator Enlist Participant2 Start LRA Track Participant1 Track Participant2 Complete on Participant1 Complete on Participant2 Notify Participants End LRA Remove LRA
- 16. Demo
- 17. #voxxed_lu Some Key code concepts • @LRA • LRA Level / defines transaction • @Compensate • Participant level: Not present, not a participant. • @Complete • Participant level • LRA ID ( = URI) • Uniquely defines the Long Running Action (transaction) • Propagated through Header
- 18. #voxxed_lu LRA Types • Required for each JAX-RS resource Active LRA No LRA Required Use Active Start New Requires New Start New Start New Mandatory Use Active Error Supports Propagate - Never Error - Not Supported Not propagated - Participant Not listed: type Nested
- 19. Demo Service A Service B Service C Start End Distributed
- 20. #voxxed_lu Returning Participant Status • Immediate • Return type ParticipantStatus, void • Asynchronous return • Return CompletableFuture<ParticipantStatus> • Idempotent @Complete/@Compensate • Return type ParticipantStatus • ParticipantStatus.Completing / ParticipantStatus.Compensating • Through @Status method • First call to @Complete/@Compensate • Following calls to @Status
- 21. #voxxed_lu TimeOut • By Default, LRA runs forever • But also by Default, immediately closed • Closed explicitly (end=true) • Define a timeout -> cancelled / all participants compensated.
- 22. #voxxed_lu Remove Participant • @Leave • Remove Participant from LRA • Developer responsible for cleanup • No @Compensate/@Complete/@Status called
- 23. #voxxed_lu Store LRA Info • LRA only performs orchestration • Participant needs to keep track of LRA • Store LRA Id as part of your business data • Extension • LRAData • ParticipantData
- 24. #voxxed_lu Takeaways • Classic approach for Transactions and Long Running Action not applicable for micro-services • MicroProfile LRA uses Compensatable actions • Loosely coupled on top of JAX-RS resources • Specification : In progress
- 25. #voxxed_lu Code • Project https://github.com/eclipse/microprofile-lra • Demo code • Released later when Payara supports MP LRA • Currently implementation phase.
- 26. #voxxed_lu Q & A
- 27. #voxxed_lu Thank You Not using the Payara Platform yet? Download the open source software: Payara Server or Payara Micro https://payara.fish/downloads Need support for the Payara Platform? https://payara.fish/support