dtornow

4 ms·

1.
Durable Executions, Defined(journal.resonatehq.io)
5 points by dtornow 10mo ago|0 comments
2.
by dtornow 10mo ago
Hey thanks for the kind words, I am happy you liked the article. You are correct, we did not come up with the rule (but Joran did come up with the name) but drew from the rich history of transaction management systems. A wonderful paper tha
3.
by dtornow 10mo ago
Yes, exceptions often surprise us in practice. The distinction I'm drawing is more about categorical boundaries than anticipated boundaries: exceptions are part of normal control flow, they are catchable and can be handled. Assertion v
4.
by dtornow 11mo ago
When we built Distributed Async Await, we went a step further: Every time the generator instance awaits, we "kill" the generator instance (you cannot really kill a generator, but you can just let it go out of scope) and create a n
5.
by dtornow 11mo ago
That's what we do at Resonate: We build Distributed Async Await, basically async await with durability provided by Durable Promises. A Durable Promises is the checkpoint (the memoization device). When the generator restarts, the genera
6.
by dtornow 11mo ago
At Resonate, we are using generators (both for the typescript sdk and the python sdk) to implement Distributed Async Await, Resonate's Durable Execution Framework. Because generators transfer control back to the caller, you can essenti
7.
The Mechanics of Async Await(blog.resonatehq.io)
3 points by dtornow 3y ago|0 comments
8.
by dtornow 3y ago
My favorite mental framework to reason about consistency in distributed systems, Invariant Confluence, was formulated by Peter Bailis at al in Coordination Avoidance in Database Systems (overview and link to paper http://www.bail
9.
The Magic of Abstractions(dominik-tornow.medium.com)
1 points by dtornow 3y ago|1 comments
10.
by dtornow 3y ago
The blog post explores the magic of abstractions using the example of database transactions.
11.
Handling Failures from First Principles(dominik-tornow.medium.com)
7 points by dtornow 4y ago|1 comments
12.
by dtornow 4y ago
Blog post presenting a blueprint for a principled failure handling strategy that aims for correctness and completeness while maximizing the chance of success even in the presence of failure. Not paywalled
13.
by dtornow 5y ago
I was part of that debate, I remember a rather interesting point of discussion: Is the main operation "apply" or "dedup" Apply seems to be the common notion of event sourcing: There is a function apply that takes a state
14.
Deep Dive into Kubernetes Network Policies(dominik-tornow.medium.com)
2 points by dtornow 6y ago|1 comments
15.
by dtornow 6y ago
With specifications in First Order Logic (TLA+ syntax)
16.
Kubernetes Networking(dominik-tornow.medium.com)
1 points by dtornow 6y ago|1 comments
17.
by dtornow 6y ago
Author here: I tried to capture networking on a conceptual level, not an implementation level. The idea is to describe the network as a graph of idealized processes and switches. If every message trace that is valid for the model is valid f