Payment System Design: Ledger, Idempotency, and Settlement
How to design a Stripe-style payment system that never charges twice, keeps an auditable ledger, and reconciles every dollar
Search across 253 posts, 23 explainers, and 84 topics
How to design a Stripe-style payment system that never charges twice, keeps an auditable ledger, and reconciles every dollar
Shared schema, schema-per-tenant, and database-per-tenant compared, plus how PostgreSQL RLS, tenant context, and hybrid tiers keep customer data safe
Why one-request-at-a-time wastes your network, and how sending many requests without waiting for replies cuts latency and lifts throughput
How a small, strongly consistent cluster lets a huge data cluster coordinate itself without drowning in consensus
How edge servers, anycast routing, and tiered caching move content close to users, cut latency, and protect your origin at global scale
A practical guide to using Cursor, the AI code editor: master Tab, Cmd+K, Chat, Agent, Plan Mode, Rules, Skills, and MCP to ship code faster
A practical guide to Cursor Agent Skills: write your first SKILL.md, scope it with paths, add scripts, and ship reusable workflows your AI agent runs on demand
How one elected leader coordinates replication so a cluster stays consistent and survives node failures
How each Git workflow handles features, releases, and hotfixes, and how to pick the one that fits your team
Why clients retry, how duplicate requests sneak in, and how to build a receiver that processes the same request twice without breaking anything
Why teams pick ULIDs over UUIDs for database keys, and how to generate and decode them
Two products, one parent company, very different jobs. Pricing, SDKs, SSO, SAML, MFA, and when each one is the right call.
The architecture behind Slack alerts, Uber ride pings, and every order confirmation email that lands on time