Tag

#distributed-systems

738 posts65 followers

Explore Hashnode

Alternatives

Shota Yamazaki20h ago · 17 min read

Sent, Accepted, Reached: Automating a Home Theater That Is Also My Office

One day I asked Alexa to shut down the theater. Alexa answered, "Shutting down the theater," and the routine ran all the way to the end. The projector stayed on. The room is my home theater with 7.1.4

2 blog.simukappu.com

Zenith Eclipse Co22h ago · 4 min read

A Shipment API Retry Needs a Shared Budget, Not Another Sleep Loop

A tracking service receives a rate-limit response. Each worker waits briefly and retries. With fifty workers, a harmless-looking local loop can keep the account above its request allowance indefinitel

zenitheclipse.hashnode.dev

Anish Ansari1d ago · 7 min read

System Design Drill Day 11: The Transactional Outbox Pattern

Almost every Laravel checkout controller has the same two lines: save the order, then dispatch a job. It works nearly every time. If Redis hiccups between those two lines, the order is paid and the em

blog.anishansari.com.np

Scott Cochran1d ago · 8 min read

TOPAK: Every Agent Is Byzantine

TL;DR TOPAK is an architecture pattern for agentic AI collaboration that is inspired by "Safe by Design" principles. T (TLA+): Formally verifiable state evolution that is testable, checkable, and som

grippinghand.dev

Anish Ansari2d ago · 7 min read

System Design Drill Day 10: Circuit Breakers, Timeouts and Degradation

The payment gateway starts timing out. The HTTP client retries, the queue retries, and workers pile up waiting on calls that won't come back. Soon pages that have nothing to do with payments are slow

2 blog.anishansari.com.np

Aritra Chakraborty2d ago · 4 min read

Netflix Conductor 4.0: Scaling Workflows to 30,000 Tasks with Asynchronous Evaluation

A workflow orchestrator can coordinate thousands of operations and still hit a scalability ceiling—not because individual tasks are too expensive, but because the engine spends too much time deciding

aidatalegends.hashnode.dev

Tobias Lang3d ago · 2 min read

Idempotency Keys: The Small Design Choice That Saves Incident Reviews

A payment endpoint retried once at the wrong moment can cost more than the outage that caused the retry. We learned that the hard way last year, and the fix was not a new service. It was one header an

2 distributed-notes.hashnode.dev

Anish Ansari4d ago · 7 min read

System Design Drill Day 9: Idempotency Keys for Payments and Retries

A customer taps "Pay" on a shaky mobile connection. The charge goes through on the server, the response never reaches the phone, and the app retries. Whether the customer is now charged twice depends

4 blog.anishansari.com.np

Zenith Eclipse Co3d ago · 4 min read

A Shipment Poller Must Commit Its Page Before Advancing Its Cursor

A shipment adapter retrieves a page of changes, saves the next cursor, then crashes before applying the page. On restart it resumes from the saved cursor. The service looks healthy, but the skipped ch

zenitheclipse.hashnode.dev

Anish Ansari5d ago · 10 min read

System Design Drill Day 8: Distributed Locks with Redis and Fencing Tokens

One unit of a hot SKU is left, and two customers press "Buy" at the same moment on two different app servers. Both see "1 in stock", both checkouts succeed, and one of them gets an apology email. A mu