--- title: "#distributed-systems articles | Hashnode" description: "Explore 769 articles tagged #distributed-systems on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/distributed-systems" --- Tag # #distributed-systems 769 posts · 65 followers [Dmytro Nasyrov](https://hashnode.com/@dmytro-nasyrov) · [10h ago](https://hashnode.com/posts/casino-wallet-recovery-session-round-ledger-state/6af425dd27d0807c65d18a8e) ### [Casino Wallet Recovery: Keep Session, Round and Ledger State Separate](https://pharos-production.hashnode.dev/casino-wallet-recovery-session-round-ledger-state?utm_source=hashnode&utm_medium=feed) A three-domain ownership map and fictional late-event sequence for assigning recovery evidence. 17 min read · [pharos-production.hashnode.dev](https://pharos-production.hashnode.dev/casino-wallet-recovery-session-round-ledger-state?utm_source=hashnode&utm_medium=feed) [TelcoEdge Inc.](https://hashnode.com/@telcoedgeinc) · [23h ago](https://hashnode.com/posts/before-the-bill-exists-how-telecom-mediation-pipelines-turn-raw-usage-into-reliable-data/6af370ff8f45796b006e8c41) ### [Before the Bill Exists: How Telecom Mediation Pipelines Turn Raw Usage Into Reliable Data](https://telcoedgeinc.hashnode.dev/before-the-bill-exists-how-telecom-mediation-pipelines-turn-raw-usage-into-reliable-data?utm_source=hashnode&utm_medium=feed) Understand how telecom mediation systems ingest, normalize, validate, deduplicate, and process network usage records before they reach billing systems 9 min read · [telcoedgeinc.hashnode.dev](https://telcoedgeinc.hashnode.dev/before-the-bill-exists-how-telecom-mediation-pipelines-turn-raw-usage-into-reliable-data?utm_source=hashnode&utm_medium=feed) [RONI DAS](https://hashnode.com/@ronidas) · [1d ago](https://hashnode.com/posts/how-canada-s-new-real-time-rail-moves-one-payment-and-what-it-teaches-about-backend-design/6af33769d90026f2051a4213) ### [How Canada's new Real-Time Rail moves one payment, and what it teaches about backend design](https://systemdesignacademy.hashnode.dev/how-canada-s-new-real-time-rail-moves-one-payment-and-what-it-teaches-about-backend-design?utm_source=hashnode&utm_medium=feed) Payments Canada switched on a 24/7 system on 9 November 2026 that settles every payment between banks in real time. Here is how one payment travels, why the fraud checks come first, and why a bank asks before it retries. 7 min read · [systemdesignacademy.hashnode.dev](https://systemdesignacademy.hashnode.dev/how-canada-s-new-real-time-rail-moves-one-payment-and-what-it-teaches-about-backend-design?utm_source=hashnode&utm_medium=feed) [Sakshi Tyagi](https://hashnode.com/@sakshityagi) · [1d ago](https://hashnode.com/posts/what-should-an-agent-remember/6af31d98fc39df3741618aae) ### [What Should an Agent Remember?](https://sakshityagi.hashnode.dev/what-should-an-agent-remember?utm_source=hashnode&utm_medium=feed) Agents That Survive Production · Part 3 of 4 Separate useful context from the durable facts needed to resume work. 7 min read · [sakshityagi.hashnode.dev](https://sakshityagi.hashnode.dev/what-should-an-agent-remember?utm_source=hashnode&utm_medium=feed) [mihalykrich](https://hashnode.com/@mkrich) · [1d ago](https://hashnode.com/posts/building-krxy-network-outage-qwen35-model-library-part-8/6af2d93c1d0be502ac51a1cb) ### [Building KRXY — Part 8: When the Network Slows Down — and the Model Library Grows](https://krxy.hashnode.dev/building-krxy-network-outage-qwen35-model-library-part-8?utm_source=hashnode&utm_medium=feed) 1–2 November 2026: two-Pi learning through bandwidth limits and a two-minute outage, followed by the first Qwen3.5 2B and 4B installations. 13 min read · [krxy.hashnode.dev](https://krxy.hashnode.dev/building-krxy-network-outage-qwen35-model-library-part-8?utm_source=hashnode&utm_medium=feed) [mihalykrich](https://hashnode.com/@mkrich) · [1d ago](https://hashnode.com/posts/building-krxy-two-nodes-distributed-learning-part-7/6af23955a301acb1ee2cc391) ### [Building KRXY — Part 7: From Two AI Nodes to Distributed Learning](https://krxy.hashnode.dev/building-krxy-two-nodes-distributed-learning-part-7?utm_source=hashnode&utm_medium=feed) 30–31 October 2026: safer node recovery, more reliable serving, and the first measured two-Pi learning and rejoin experiments. 12 min read · [krxy.hashnode.dev](https://krxy.hashnode.dev/building-krxy-two-nodes-distributed-learning-part-7?utm_source=hashnode&utm_medium=feed) [Tony Dzi (Anton Dziatkovskii)](https://hashnode.com/@tonydzi) · [3d ago](https://hashnode.com/posts/coordination-decay-103-days-of-a-seven-machine-llm-agent-fleet/6af0904e890d44c33ac66f88) ### [Coordination Decay: 103 Days of a Seven-Machine LLM Agent Fleet](https://tonydzi.hashnode.dev/coordination-decay-103-days-of-a-seven-machine-llm-agent-fleet?utm_source=hashnode&utm_medium=feed) A coordination protocol can keep its checked safety rules and still fall out of use. That is the main thing we learned from running LLM coding agents on seven machines for 103 days, and it is why we a 7 min read · [tonydzi.hashnode.dev](https://tonydzi.hashnode.dev/coordination-decay-103-days-of-a-seven-machine-llm-agent-fleet?utm_source=hashnode&utm_medium=feed) [Hussain Fakhruddin](https://hashnode.com/@hussainanjar) · [3d ago](https://hashnode.com/posts/recurring-jobs-for-mena-saas-missed-runs-and-catch-up/6af0599d687733d974aa63a2) ### [Recurring jobs for MENA SaaS: missed runs and catch-up](https://www.sultanbyte.com/recurring-jobs-for-mena-saas-missed-runs-and-catch-up?utm_source=hashnode&utm_medium=feed) Design recurring work with durable occurrence identities, explicit missed-run policies and controlled recovery for Saudi and UAE deployments. 9 min read · [sultanbyte.com](https://www.sultanbyte.com/recurring-jobs-for-mena-saas-missed-runs-and-catch-up?utm_source=hashnode&utm_medium=feed) [Amitabh](https://hashnode.com/@prepd-tech) · [3d ago](https://hashnode.com/posts/from-one-server-to-many-what-each-scaling-step-fixes-and-what-it-breaks/6af06f526bd10e54d995b180) ### [From One Server to Many: What Each Scaling Step Fixes, and What It Breaks](https://prepd.hashnode.dev/from-one-server-to-many-what-each-scaling-step-fixes-and-what-it-breaks?utm_source=hashnode&utm_medium=feed) Most system design answers jump straight to the final architecture. Interviewers are more interested in the path: what broke at each stage, which change fixed it, and what that change made harder. Her 3 min read · [prepd.hashnode.dev](https://prepd.hashnode.dev/from-one-server-to-many-what-each-scaling-step-fixes-and-what-it-breaks?utm_source=hashnode&utm_medium=feed) [RONI DAS](https://hashnode.com/@ronidas) · [3d ago](https://hashnode.com/posts/how-github-rebuilt-git-storage-for-5-000-agents-on-one-repo/6aef750f8c6f0da3e2501ab8) ### [How GitHub rebuilt Git storage for 5,000 agents on one repo](https://systemdesignacademy.hashnode.dev/how-github-rebuilt-git-storage-for-5-000-agents-on-one-repo?utm_source=hashnode&utm_medium=feed) GitHub split Git into immutable packs in Azure Blob Storage and a tiny compare-and-swap log for refs. In testing it took 7,200 pushes a second on one repository. Here is how, in plain words. 8 min read · [systemdesignacademy.hashnode.dev](https://systemdesignacademy.hashnode.dev/how-github-rebuilt-git-storage-for-5-000-agents-on-one-repo?utm_source=hashnode&utm_medium=feed)