Skip to content
José da Cruz

Enterprise Architect, and Life Thinker

José da Cruz

Enterprise Architect, and Life Thinker

Tag: system design

architecture

Designing a Distributed Session Store: Why Sticky Sessions Break Under Load

josedacruz, November 6, 2026November 6, 2026

TL;DR: Sticky sessions keep a user’s login and cart data glued to whichever server first handled their request. It’s simple to set up, but it quietly breaks the moment you restart a server, deploy new code, or add more servers to handle traffic. Moving session data out of the app…

Continue Reading
architecture

The Five-Minute Rule: A Heuristic for Deciding What Belongs in Cache

josedacruz, October 24, 2026October 24, 2026

TL;DR: The “five-minute rule” is an old database heuristic that says: cache something if the cost of keeping it in memory is lower than the cost of re-fetching it, given how often it gets used. The actual “five minutes” number from the 1980s doesn’t matter anymore — what still matters…

Continue Reading
architecture

GitHub Weekly: Architecture & Infra Tools Worth a Look (September 14 – September 20, 2026)

josedacruz, September 21, 2026September 21, 2026

TL;DR: This week we’re setting aside the usual overall-trending list to spotlight repos tagged around architecture, system design, diagramming, and infrastructure-as-code — the stuff most relevant to readers thinking about how systems are put together. The standout theme: a cluster of new “diagram-as-code” tools built specifically as skills for AI…

Continue Reading
architecture

Designing a Real-Time Leaderboard: Why Sorted Sets Beat a SQL ORDER BY at Scale

josedacruz, September 16, 2026September 16, 2026

TL;DR: A leaderboard looks like a simple feature — sort some scores, show the top N — but a plain SQL table falls over once you have millions of players updating scores in real time. The fix isn’t a bigger database, it’s a different data structure: a sorted set (like…

Continue Reading
architecture

The Saga Pattern: How to Undo a Transaction That Spans Five Services

josedacruz, September 16, 2026September 16, 2026

TL;DR: A saga is how you handle a “transaction” that spans multiple services, since you can’t wrap them all in one database commit. Instead of one atomic rollback, you run a chain of local steps and, if something downstream fails, you undo the earlier steps with separate “compensating” actions. It’s…

Continue Reading
architecture

Designing a Webhook Delivery System: Why Your Retries Need an Idempotency Key

josedacruz, September 13, 2026September 13, 2026

TL;DR: A webhook is just an HTTP POST your system sends to someone else’s server when something happens, but “just an HTTP POST” hides a lot of hard problems. Networks drop packets, receivers time out, and retries create duplicates — so a webhook delivery system that actually works needs retries…

Continue Reading
architecture

Designing a Distributed Counter: Why Global Counts Don’t Scale

josedacruz, September 10, 2026September 10, 2026

TL;DR: A single database row that stores a count (likes, views, votes) works fine until enough people hit it at once — then it becomes a bottleneck that slows down or breaks your whole app. The fix isn’t a bigger database, it’s splitting the count into several pieces that get…

Continue Reading
architecture

Designing a Distributed Job Scheduler: Why “Just Use Cron” Doesn’t Scale

josedacruz, August 26, 2026August 26, 2026

TL;DR: A single cron job looks simple until the server it lives on goes down, and “just add a second cron server” quietly turns into a duplicate-execution bug. A real distributed job scheduler needs a shared source of truth for what’s due, a way for exactly one worker to claim…

Continue Reading
architecture

The Rule of Least Power: Why the Boring Technology Choice Usually Wins

josedacruz, August 19, 2026August 19, 2026

TL;DR: When you’re picking a tool, a database, or a way of solving a problem, the option with the most features and the most flexibility isn’t automatically the right choice. The Rule of Least Power says: pick the least powerful tool that still gets the job done, because less powerful…

Continue Reading
architecture

The Distributed Monolith: When Your Microservices Still Deploy as One App

josedacruz, August 18, 2026August 18, 2026

TL;DR: Splitting a monolith into microservices doesn’t automatically get you the benefits people promise — independent deploys, one team’s mistake not taking down everyone else, services that scale on their own. If your new services still call each other synchronously, share a database, or all have to deploy together, you’ve…

Continue Reading
  • 1
  • 2
  • Next
  • architecture (167)
  • artificial-intelligence (6)
  • books (2)
  • courses (4)
  • decision-frameworks (4)
  • finances (1)
  • java (8)
  • life-improvement (20)
  • metrics (3)
  • observability (2)
  • puzzles and challenges (3)
  • reviews (1)
  • security (8)
  • Soft Skills (1)
  • spring-boot (36)
  • Systems Thinking (3)
  • GitHub Weekly: AI Agent Tools Trending Right Now (November 2 – November 8, 2026)
  • Designing a Distributed Session Store: Why Sticky Sessions Break Under Load
  • Essential Reading: Release It! — Why Production Is a Different Game Than Development
  • GitHub Weekly: Top 10 Trending Repos (October 26 – November 1, 2026)
  • GitHub Weekly: Architecture & Infra Tools Worth a Look (October 19 – October 25, 2026)
©2026 José da Cruz | WordPress Theme by SuperbThemes