Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Have each component of the system participate in the decision-making process about the workflow of a business transaction, instead of relying on a central point of control : https://docs.microsoft.com/en-us/azure/architecture/patterns/choreography

  1. Context and problem

    We need to make different small services to work together in order to process a business transaction end-to-end, reducing point-to-point communication between the services.

  2. Solution

    Choreography pattern allows a transaction to be executed in parallel steps and/or in sequences.

    Features : Execution is sequenced by orders and/or events; each step of choreography becomes a consumable command/event; each process is responsible for subscribing to the required topic; coordination is decentralized.

  3. Challenges

  • No labels