Tag feed

#distributed-system

1,037 posts369 followers

Explore Hashnode

Alternatives

Trending tags this week

NHNasim Hossain Rabbiblog.nasimhossain.dev1d ago · 10 min read

Little's Law: The Formula Behind Every Good System Design Interview

You're in a system design interview and you're asked to design a banking application. Customers can: Login View accounts Check transactions Transfer money Download statements The interviewer ad

0

SKsandeep kesarwanimusashiforge.hashnode.dev2d ago · 10 min read

Postgres as a Queue

I've run Celery on RabbitMQ in production for years and every so often wonder whether the broker could just be Postgres. It can, and two Go libraries do it well. But a table isn't a broker, and three

0

IMIhar Maiseyeuiharmaiseyeu.net6d ago · 12 min read

Saga Pattern: Coordinating Transactions Across Microservices

Introduction In a monolithic application, transactions are straightforward: if something fails, you roll back the entire operation. But in a microservices architecture, where each service owns its dat

0

PNPriyansh Naskarpriyanshucodes.hashnode.devSep 7 · 5 min read

Rate Limiting from Scratch in Go: Where Each Algorithm Breaks

A rate limiter restricts the intended or un-intended access to a system. In this article we dive deep into the intuition between different types of rate limiting algorithms and their pros/cons. For th

0

Iihorholiakihorholiak.hashnode.devSep 7 · 5 min read

ACCORD - Leaderless consensus

Several days ago, I was casually scrolling through LinkedIn, ranting as always about how a professional network had become a social network, when I stumbled upon a post claiming that Cassandra is addi

0

MKmreza karidiveintotechkari.hashnode.devSep 6 · 6 min read

Behind the Button: How Online Payments Work — and Why They’re Hard to Scale

You press Pay. A few seconds later, you see Payment successful. It feels simple. Behind that button, however, several banks, payment networks, databases, and security systems have to agree on one very

0

BBizTechLabbiztechlab.hashnode.devSep 4 · 12 min read

Your API Can Retry. Your Business Can't.

A retry is technically safe only when repeating the request is business-safe — and most systems retry first, ask that question never. The Retry That Looks Harmless Every engineer has written this code

0

SGSui Gnneurons-me.hashnode.devSep 4 · 2 min read

Centralize the self, Distribute the data

Pure decentralization often introduces unnecessary friction, high latency, and UX overhead. A federated approach provides sovereign control over identity while leveraging a distributed mesh for execut

0

BABetini Akarandutbetiniakarandut.hashnode.devSep 2 · 23 min read

Building Offline-First Systems for Low-Connectivity Environments: Architecture Lessons from Nigerian Agritech

A note on the architecture This article describes lessons from a production agricultural technology platform. Some implementation details, operational parameters, identifiers, and business-specific lo

0

SUSandesh Upadhayayengineeringlair.hashnode.devSep 1 · 20 min read

I Built Kafka From Scratch to Understand how it actually works

But Why?? I had used Kafka enough to know the terminology: topics, partitions, producers, consumers, replication. But knowing the pieces is different from understanding why they fit together the way t

0

#distributed-system

Search Hashnode

#distributed-system

Explore Hashnode

Trending tags this week

Little's Law: The Formula Behind Every Good System Design Interview

Postgres as a Queue

Saga Pattern: Coordinating Transactions Across Microservices

Rate Limiting from Scratch in Go: Where Each Algorithm Breaks

ACCORD - Leaderless consensus

Behind the Button: How Online Payments Work — and Why They’re Hard to Scale

Your API Can Retry. Your Business Can't.

Centralize the self, Distribute the data

Building Offline-First Systems for Low-Connectivity Environments: Architecture Lessons from Nigerian Agritech

I Built Kafka From Scratch to Understand how it actually works