Skip to content

Latest commit

 

History

History
9 lines (5 loc) · 1.27 KB

additional-patterns.md

File metadata and controls

9 lines (5 loc) · 1.27 KB
Raw

Architecture: Additional patterns applied

  • Async HTTP APIs: Designing an API that provides s synchronous HTTP response in the context of Saga is not best approach, as Saga is designed for long-lived transactions (i.e. long-running operations). The Async HTTP API pattern is used to address this problem, where Saga Client triggers the long-running action and redirects the client to a status endpoint that allows the client to poll it to know when the transaction is finished.

  • Retry: Pattern used on producing messages to Event Hubs and activities calls from the orchestrator.

  • Circuit Breaker: Pattern integrated with Retry on producing messages to Event Hubs.

  • Database-per-microservice: Pattern used to ensure that each Saga participant manages your own data decoupled from other participants.