<h1 id="durable-execution">Durable Execution<a aria-hidden="true" class="anchor-heading icon-link" href="#durable-execution"></a></h1>
<h2 id="story">Story<a aria-hidden="true" class="anchor-heading icon-link" href="#story"></a></h2>
<ul>
<li>After Amazon (one of the first large adopters of microservices) decided that using message queues to communicate between services was not the way to go (hear the story first-hand <a href="https://www.youtube.com/watch?v=wIpz4ioK0gI">here</a>), they started using orchestration. And once they realized defining orchestration logic in YAML/JSON wasn’t a good developer experience, they created <a href="https://docs.aws.amazon.com/amazonswf/latest/developerguide/swf-welcome.html">AWS Simple Workfow Service</a> to define logic in code. This technique of backing code by an orchestration engine is called durable execution, and it spread to <a href="https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-overview?tabs=csharp-inproc">Azure Durable Functions</a>, <a href="https://cadenceworkflow.io/">Cadence</a> (used at Uber for <a href="https://www.uber.com/blog/announcing-cadence/">> 1,000 services</a>), and <a href="https://temporal.io/">Temporal</a> (used by Stripe, Netflix, Datadog, Snap, Coinbase, and many more).</li>
</ul>
<h2 id="references">References<a aria-hidden="true" class="anchor-heading icon-link" href="#references"></a></h2>
<ul>
<li><a href="https://temporal.io/blog/time-travel-debugging-production-code">https://temporal.io/blog/time-travel-debugging-production-code</a></li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/wiki/notes/ntoplz1ephb277ktutqibro">Temporal</a></li>
</ul>

Durable Execution

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]]  