https://vacua.dev/tags/distributed-systems/Recent content in Distributed-Systems on Brian FaustHugoen-USMon, 01 Jan 0001 00:00:00 +0000https://vacua.dev/thoughts/a-transaction-defines-what-must-succeed-together/Wed, 01 Feb 2017 00:00:00 +0000https://vacua.dev/thoughts/a-transaction-defines-what-must-succeed-together/<p>A booking flow reserved funds, completed the remote booking, and captured the funds. Only then did synchronous response processing fail.</p> <p>The remote booking existed. The funds were captured. The caller received a failure.</p> <p>The capture was individually valid, and its own database transaction committed cleanly. It was still too early. We had drawn the success boundary around “remote booking returned” while the operation promised something larger: a complete booking result which the caller could use.</p>https://vacua.dev/thoughts/a-correlation-identifier-is-a-boundary-contract/Thu, 01 Sep 2016 00:00:00 +0000https://vacua.dev/thoughts/a-correlation-identifier-is-a-boundary-contract/<p>A shipment request failed somewhere after payment and before its documents were ready. The application, queue worker, and remote adapter all had logs. None of them shared an identifier.</p> <p>The search began with timestamps, account details, and values which looked related. Payment was a plausible lead. So were several nearby remote calls. Some trails ended only after hours of reading because they belonged to different requests which happened at nearly the same time.</p>