← Extractions

How To Ensure Systems Do What We Want And Take Care Of Themselves — wroclove.rb 2022

Michał Zajączkowski de Mezer's wroclove.rb 2022 talk on designing self-healing components via the 'at-least-once + idempotence' recipe. Covers delivery semantics, retry strategies with backoff, and protocol-level idempotence using optimistic locking and idempotency keys for HTTP GET/DELETE/PUT/POST patterns. Q&A explores race conditions on retry, third-party APIs without idempotency keys, and sharding as a CAP-theorem response.

Model

claude-opus-4-7

Ingestion

d4cd6ec9

Input tokens

191,460

fresh: 96,348
cached: 83,349
cache write: 11,763

Output tokens

11,125

Duration

176.1s

Roundtrips

Tool calls

Cost

$0.00

Nodes/edges extracted

23 / 38

Read set (nodes/edges)

72 / 22

Nodes (23)

create Michał Bronikowski person

kind (empty) → person

name (empty) → Michał Bronikowski

slug (empty) → michal-bronikowski

description (empty) → Community member thanked at the opening of the talk for contacting the speaker and arranging the invitation to give t...

short_description (empty) → wroclove.rb community member who invited the speaker.

update Michał Zajączkowski de Mezer person

attrs (empty) → {"role" => "back-end engineer"}

description Conference speaker. → Back-end engineer working at Nagarro. Speaker at wroclove.rb 2022 with a language-agnostic talk (no Ruby code) on des...

short_description Conference speaker. → Back-end engineer at Nagarro; speaker on distributed-systems reliability.

create Nagarro company

kind (empty) → company

name (empty) → Nagarro

slug (empty) → nagarro

attrs (empty) → {"industry" => "IT services"}

description (empty) → IT services company where Michał Zajączkowski de Mezer works as a back-end engineer. Transcribed as 'naguro' in the t...

short_description (empty) → IT services and consulting company.

update How To Ensure Systems Do What We Want And Take Care Of Themselves talk

attrs {"type" => "talk"} → {"date" => "2022-03-11", "type" => "talk"}

description Talk at wroclove.rb 2022. → Michał Zajączkowski de Mezer's wroclove.rb 2022 talk. Language-agnostic with no code — a message-passing abstraction ...

short_description Talk at wroclove.rb 2022. → wroclove.rb 2022 language-agnostic talk on at-least-once + idempotence for self-healing systems.

create At-Least-Once Plus Idempotence Recipe concept

kind (empty) → concept

name (empty) → At-Least-Once Plus Idempotence Recipe

slug (empty) → at-least-once-plus-idempotence-recipe

attrs (empty) → {"category" => "pattern"}

description (empty) → The talk's central recipe for building self-healing systems. The sender guarantees at-least-once delivery via retries...

short_description (empty) → Reliability recipe: combine at-least-once delivery with idempotent receivers to achieve exactly-once effect.

create Delivery Semantics concept

kind (empty) → concept

name (empty) → Delivery Semantics

slug (empty) → delivery-semantics

attrs (empty) → {"category" => "pattern"}

description (empty) → Three processing guarantees / delivery semantics. At-most-once: trigger an action once and never retry — risk is the ...

short_description (empty) → Modes of execution: at-most-once, at-least-once, exactly-once.

create Exponential Backoff concept

kind (empty) → concept

name (empty) → Exponential Backoff

slug (empty) → exponential-backoff

attrs (empty) → {"category" => "pattern"}

description (empty) → Popular backoff strategy for retries. Instead of dense constant retries (which risk killing an already-overloaded rec...

short_description (empty) → Retry strategy where wait between attempts grows exponentially.

create Expected vs Unexpected Errors concept

kind (empty) → concept

name (empty) → Expected vs Unexpected Errors

slug (empty) → expected-vs-unexpected-errors

attrs (empty) → {"category" => "practice"}

description (empty) → Errors fall into two buckets: expected ones (known error bodies from a third party you've learned to handle) and unex...

short_description (empty) → Distinction between known/handled errors and novel ones, for alerting purposes.

create Protocol Thinking concept

kind (empty) → concept

name (empty) → Protocol Thinking

slug (empty) → protocol-thinking

attrs (empty) → {"category" => "methodology"}

description (empty) → Discipline of moving past happy-path thinking when designing the application-level protocols components use to commun...

short_description (empty) → Designing application protocols by reasoning about every failure point, not the happy path.

create Optimistic Locking concept

kind (empty) → concept

name (empty) → Optimistic Locking

slug (empty) → optimistic-locking

attrs (empty) → {"category" => "pattern"}

description (empty) → Solution to the lost-update / mid-air-collision race condition that arises when multiple senders can change the same ...

short_description (empty) → Concurrency control using a version parameter to detect and reject stale updates.

create Lost Update Problem concept

kind (empty) → concept

name (empty) → Lost Update Problem

slug (empty) → lost-update-problem

attrs (empty) → {"category" => "pattern"}

description (empty) → Race condition, also called mid-air collision, that occurs when two senders read the same state, make independent dec...

short_description (empty) → Race condition where concurrent writes overwrite each other's changes.

create Idempotency Key concept

kind (empty) → concept

name (empty) → Idempotency Key

slug (empty) → idempotency-key

attrs (empty) → {"category" => "pattern"}

description (empty) → Convention for making POST-style creation idempotent. The sender generates (or retrieves) a unique token representing...

short_description (empty) → Unique client-generated token that lets a receiver detect and ignore duplicate create requests.

create Find-or-Create Pattern concept

kind (empty) → concept

name (empty) → Find-or-Create Pattern

slug (empty) → find-or-create-pattern

attrs (empty) → {"category" => "pattern"}

description (empty) → Fallback pattern when a third-party API supports neither idempotency keys nor sender-chosen IDs: before creating, que...

short_description (empty) → Read-check-write fallback for creation without idempotency-key support.

create HTTP Method Idempotence concept

kind (empty) → concept

name (empty) → HTTP Method Idempotence

slug (empty) → http-method-idempotence

attrs (empty) → {"category" => "pattern"}

description (empty) → Analysis of HTTP verbs through a protocol-thinking lens. GET (read): idempotent — retries are always safe because no ...

short_description (empty) → Which HTTP verbs are idempotent and under what assumptions.

create Sharding concept

kind (empty) → concept

name (empty) → Sharding

slug (empty) → sharding

attrs (empty) → {"category" => "architecture"}

description (empty) → Scale-out technique in which data is divided across partitions using a deterministic function (e.g. a hash of the ent...

short_description (empty) → Partitioning data/requests across nodes by a deterministic hash to scale writes.

create Use at-least-once plus idempotence to build self-healing systems takeaway

kind (empty) → takeaway

name (empty) → Use at-least-once plus idempotence to build self-healing systems

slug (empty) → use-at-least-once-plus-idempotence-to-build-self-healing-systems

attrs (empty) → {"type" => "recommendation"}

description (empty) → The one-slide takeaway of the talk: if you remember only one thing, use the recipe 'at-least-once + idempotence' at e...

short_description (empty) → Combine at-least-once delivery with idempotent receivers so systems resume and self-heal.

create Don't kill dependencies — use backoff takeaway

kind (empty) → takeaway

name (empty) → Don't kill dependencies — use backoff

slug (empty) → don-t-kill-dependencies-use-backoff

attrs (empty) → {"type" => "warning"}

description (empty) → Every retry reserves CPU and memory on the receiver. If the receiver is already close to out-of-memory, aggressive co...

short_description (empty) → Retries without backoff can push an already-struggling receiver over the edge.

create Don't kill your team — alert only on unexpected errors takeaway

kind (empty) → takeaway

name (empty) → Don't kill your team — alert only on unexpected errors

slug (empty) → don-t-kill-your-team-alert-only-on-unexpected-errors

attrs (empty) → {"type" => "recommendation"}

description (empty) → Flooding error-monitoring tools (Rollbar, Sentry) with expected third-party exceptions burns developer cycles for no ...

short_description (empty) → Only page the team on unexpected errors; use metrics/alarms for the expected ones.

create Tune retry duration to the actor takeaway

kind (empty) → takeaway

name (empty) → Tune retry duration to the actor

slug (empty) → tune-retry-duration-to-the-actor

attrs (empty) → {"type" => "recommendation"}

description (empty) → Decide how long to retry based on who initiated the communication. For human users, UX beats durability — retry one t...

short_description (empty) → Humans want fast feedback; machines should retry for days so systems self-heal.

create Negotiate for idempotency-key support takeaway

kind (empty) → takeaway

name (empty) → Negotiate for idempotency-key support

slug (empty) → negotiate-for-idempotency-key-support

attrs (empty) → {"type" => "recommendation"}

description (empty) → When integrating with a third party that supports neither idempotency keys nor find-or-create nor sender-chosen IDs, ...

short_description (empty) → If a third-party API lacks idempotency support, negotiate the feature or switch providers.

create How should POST retries handle changed source-of-truth state? question

kind (empty) → question

name (empty) → How should POST retries handle changed source-of-truth state?

slug (empty) → how-should-post-retries-handle-changed-source-of-truth-state

attrs (empty) → {"answer_summary" => "Apply optimistic locking with a version parameter; receiver compares the incoming version and a...

description (empty) → Audience question: when a POST depends on some entity that may have been updated between the initial attempt and the ...

short_description (empty) → On retry, should the sender re-POST with updated parameters from the meanwhile-changed entity?

create Handling third-party APIs without idempotency keys question

kind (empty) → question

name (empty) → Handling third-party APIs without idempotency keys

slug (empty) → handling-third-party-apis-without-idempotency-keys

attrs (empty) → {"answer_summary" => "PUT with a sender-chosen UUID if supported; otherwise negotiate with the provider or switch API...

description (empty) → Audience question: when a third-party API doesn't support idempotency keys and the find-or-create technique is imprac...

short_description (empty) → How to guarantee single creation when neither idempotency keys nor efficient find-or-create exist?

create Scaling receivers vs implementing idempotency question

kind (empty) → question

name (empty) → Scaling receivers vs implementing idempotency

slug (empty) → scaling-receivers-vs-implementing-idempotency

attrs (empty) → {"answer_summary" => "Yes — it's the CAP theorem at work. Solve the partitioning dimension with sharding: route each ...

description (empty) → Audience observation: race conditions happen under load, which pushes receivers to scale out, which makes the atomic/...

short_description (empty) → Does scaling receivers under race-condition load make idempotency harder to implement?

Edges (38)

update Michał Zajączkowski de Mezer → authored → How To Ensure Systems Do What We Want And Take Care Of Themselves

context (empty) → Single-speaker presentation delivered at wroclove.rb 2022.

update How To Ensure Systems Do What We Want And Take Care Of Themselves → presented_at → wroclove.rb 2022

context (empty) → Talk delivered at wroclove.rb 2022 on 2022-03-11.

create Michał Zajączkowski de Mezer → works_at → Nagarro

attrs (empty) → {"role" => "back-end engineer"}

context (empty) → Speaker introduces himself as a back-end engineer at Nagarro.

relation (empty) → works_at

source_node_id (empty) → a91c84e8-bda1-4056-b7ad-7b890e00deb8

target_node_id (empty) → 43724f5d-e9d2-461f-8b4d-09b26d1f3229

create Michał Zajączkowski de Mezer → attended → wroclove.rb 2022

context (empty) → Speaker at the conference.

relation (empty) → attended

source_node_id (empty) → a91c84e8-bda1-4056-b7ad-7b890e00deb8

target_node_id (empty) → cfc5cfd3-25a6-46c2-8b5d-626986c71c24

create Michał Bronikowski → attended → wroclove.rb 2022

context (empty) → Thanked at the talk opening for contacting the speaker and arranging the invitation.

relation (empty) → attended

source_node_id (empty) → 7149f222-3e48-472a-b6b6-1aaa816b52a5

target_node_id (empty) → cfc5cfd3-25a6-46c2-8b5d-626986c71c24

create How To Ensure Systems Do What We Want And Take Care Of Themselves → about → At-Least-Once Plus Idempotence Recipe

context (empty) → Recipe is the central thesis of the talk.

relation (empty) → about