<h1 id="choreography">Choreography<a aria-hidden="true" class="anchor-heading icon-link" href="#choreography"></a></h1>
<p><img src="/wiki/assets/images/2023-10-06-14-21-19.png"></p>
<ul>
<li>harder to reason about, because reactions can happen anywhere in the system</li>
</ul>
<h2 id="vs-orchestration">vs <a href="/wiki/notes/08k9bzf078nrt71hp1rxaao">Orchestration</a><a aria-hidden="true" class="anchor-heading icon-link" href="#vs-orchestration"></a></h2>
<ul>
<li>"Orchestration is a centralized approach to making all control decisions about interactions between services. Here a central orchestrator service coordinates all of the other services that execute a business transaction or workflow. By contrast, a choreography is a decentralized approach to coordinating this workflow, where each service determines its own behavior based on the messages it receives from other services."</li>
</ul>
<h2 id="implementations">Implementations<a aria-hidden="true" class="anchor-heading icon-link" href="#implementations"></a></h2>
<ul>
<li><a href="/wiki/notes/vmuutz9km59eyd7qxs6c8p2">MassTransit</a> c#</li>
</ul>
<h2 id="resources">Resources<a aria-hidden="true" class="anchor-heading icon-link" href="#resources"></a></h2>
<ul>
<li><a href="https://www.infoworld.com/article/3687638/orchestration-and-choreography-in-net-microservices.html">https://www.infoworld.com/article/3687638/orchestration-and-choreography-in-net-microservices.html</a></li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/wiki/notes/rsqds8jgt1igv9c2hr5bp0j">Tekton</a></li>
<li><a href="/wiki/notes/08k9bzf078nrt71hp1rxaao">Orchestration</a></li>
<li><a href="/wiki/notes/3fh0o75ztyvi7sqq2xqkp2s">Fantastic Nine</a></li>
</ul>

Choreography

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  

Choreography

vs Orchestration

Implementations

Resources