Tag feed

#distributed-system

1,053 posts369 followers

Explore Hashnode

Alternatives

Trending tags this week

AMAhmed Mahsookahmedmahsook.hashnode.dev5h ago · 8 min read

Building a Financially Correct Wallet and Settlement System in Go

When I started building PriceFlow's wallet, I assumed the hard part would be CRUD: add money, subtract money, done. It wasn't. The hard part was defining what "correct" actually means when money is in

0

FFFred Fengfredfeng.hashnode.dev5h ago · 7 min read

Vortex TSDB: Live Metrics in One Command

HTTP Writes, Minute Aggregates, Sliding Windows, Replicated in Memory 1. Overview Lightweight. Replicated. Real-time. Vortex TSDB is a distributed time series database for live metrics. Push numbers

0

HGHarrison Guoharrisonsec.hashnode.dev2d ago · 9 min read

Webhook Security Is Distributed Systems Security

A webhook looks like the easiest thing in your system. A provider sends you a POST, you read the JSON, you do the thing. Three lines. It is one of the most dangerous. Not because the parsing is hard,

1

M

DPDevesh Parmarbackend-bytes.hashnode.dev2d ago · 7 min read

Database Sharding: What Happens When One Database Isn't Enough?

Imagine you're the engineer at Notion. I have no idea how their stack actually looks inside, so treat this as a thought experiment. Your product has hundreds of millions of users, and everything lives

0

MTMohammad Talimtalim.hashnode.dev2d ago · 19 min read

I Built a Distributed Task Queue in from Scratch in Go and PostgreSQL

I built Dhara, a distributed task queue for Go, using PostgreSQL as the only queue and source of truth. No Redis, no Kafka, no RabbitMQ. In this post I'll cover why I built it, how a task moves throug

0

EKErnest Khasanzhinovernest-khas.hashnode.dev4d ago · 19 min read

SporeMachine: Building a Harmless Botnet in Go

1. Introduction As a kid, and later in college, I devoured technical articles about botnets and how their nodes communicate. What fascinated me was how individual agents, each running on its own machi

0

MBMadhav Bhasinblog.madhav.dev4d ago · 6 min read

Redis Patterns Every Backend Engineer Should Know

Redis gets reached for because it's fast. That's often the wrong reason. Speed isn't a pattern — it's a property. Using Redis correctly means understanding what each pattern is actually good at and, j

0

PNPriyansh Naskarpriyanshucodes.hashnode.dev6d ago · 6 min read

A Practical Guide to Failure Handling

Think about a situation where you have are maintaining an e-commerce site. A customer clicks Pay on your checkout page. The loader takes 10 seconds then an error message pops up and says "Something we

0

KMKrishnam Murarkaedilec-engineering.hashnode.devSep 28 · 4 min read

Dead-letter replay is a production write, not queue administration

Dead-letter replay looks like queue administration and behaves like a production write. The handler that failed on a message may have done most of its work before it threw: charged a card, sent an ema

1

I

HGHarrison Guoharrisonsec.hashnode.devSep 27 · 11 min read

Validation Is a Loop, Not an Assertion: Why Your AI Agent Reports Success It Never Achieved

An agent I was reviewing was asked to rename a function across a repository. It ran for a while, made its edits, and returned a clean summary: Done. Renamed parseUser to parseAccount everywhere. The s

2

G

#distributed-system

Search Hashnode

#distributed-system

Explore Hashnode

Trending tags this week

Building a Financially Correct Wallet and Settlement System in Go

Vortex TSDB: Live Metrics in One Command

Webhook Security Is Distributed Systems Security

Database Sharding: What Happens When One Database Isn't Enough?

I Built a Distributed Task Queue in from Scratch in Go and PostgreSQL

SporeMachine: Building a Harmless Botnet in Go

Redis Patterns Every Backend Engineer Should Know

A Practical Guide to Failure Handling

Dead-letter replay is a production write, not queue administration

Validation Is a Loop, Not an Assertion: Why Your AI Agent Reports Success It Never Achieved