DIGNALEGI

Software Architecture

A personal, scored reading index

A focused reading list

Architecture earns its keep by making change safer.

These essays treat architecture as a set of consequential technical choices: boundaries, failure modes, data, operations, and the cost of changing a system over time.

Use this map

Draw the boundaryDecide what must change together and what needs an explicit contract.
Expose the failure modeTrace how data, dependencies, load, and recovery behave when the happy path ends.
Price future changeCompare today's simplicity with the operational and migration costs the choice creates.
Software Architecture / From the index

Redis is not a map you talk to over TCP

blog.verygoodsoftwarenotvirus.dev via Lobsters September 2026

Why read thisRedis abstractions become unsafe when slots, batching, expiry semantics, and serialization costs quietly become load-bearing.

Some background helpful · Summary available

Open reading room
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence appears substantive and complete, but the judgment is limited to the provided extracted text.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
An exploded mechanical assembly meets fragments of a technical drawing.
02

How we halved DNS build delay and cut memory use by 85%

Why read thisSmaller DNS rebuilds require explicit knowledge of dependencies and old state; their memory savings can also make protective waiting periods safely shorter.

Some background helpful · Summary available

Cloudflare Blog November 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The supplied text contains sampling gaps; omitted sections and visuals were not assessed. Results rely on internal measurements: the 24-hour scheduler comparison and subsequent delay reductions from changed safeguards have different evidential scopes.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
03

Inside GitHub’s new Git storage architecture

Why read thisGitHub’s storage redesign concentrates agreement on small reference updates, allowing repository data, request handling, and maintenance to scale independently.

Some background helpful · Summary available

GitHub Blog via Hacker News (100+ points) · Lobsters November 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The text is sampled, with missing compaction details and unseen charts; throughput figures come from internal testing with limited benchmark methodology.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
04

Your Agent Isn't Dumb. Your Tools Are.

Why read thisAgent failures blamed on prompts may actually come from vague tool contracts that force guessing before execution.

Some background helpful · Summary available

thetshaped.dev
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The evidence appears to contain the full text, though it also includes some sponsor and promotional sections.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →

Software Architecture archive

Filter by score
70+

36 pieces · Highest scores first.

05

How to name things

Why read thisNames are compressed explanations of system meaning, and choosing them can expose hidden ambiguities in data models and behavior.

Some background helpful · Summary available

kolemannix.com August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The evidence is substantial and argument-dense; its value comes from experience and conceptual analysis rather than research support.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
06

Hatchet

Why read thisPostgres reliability depends on designing around indexes, locks, planner estimates, connection costs, dead tuples, and migration blocking.

Some background helpful · Summary available

hatchet.run
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The evidence demonstrates technical depth; additional details in external links were not assessed.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
07

Hardening Container Images

Why read thisContainer hardening means reducing exploitable surface, post-compromise execution, unnoticed drift, and unverifiable builds, not merely shrinking an image.

Technical reading · Summary available

grepular.com via Lobsters September 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The argument relies on one PowerDNS Recursor image; the author notes some limits to its generalisability.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
08

From 2,500 requests to 24: Rebuilding star history without the stargazers

Why read thisSmaller API responses can leave database costs unchanged: GitHub made star history cheaper by filtering records before counting them.

Some background helpful · Summary available

GitHub Blog October 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Performance figures are reported in the supplied article text and are not independently verified; referenced charts are not provided.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
09

The Wrong Abstraction

Why read thisShared code can become harder to change than duplicated code when new requirements turn a common operation into a collection of exceptions.

Software design essay · Some background helpful · Summary available

sandimetz.com via Editor’s archive
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The provided text develops the mechanism and repair procedure but includes no detailed code case or comparative outcomes; its categorical claim about conditional paths exceeds the demonstrated support.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
10

From the Software Architecture index

Everything I know about good API design

Why read thisGood API design stays boring because public interfaces are hard to change and costly to break.

Brief pending · original available

seangoedecke.com via Editor’s archive · Raindrop · Programming Digest September 2025
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, so the score reflects the visible argument and examples, not a complete judgment of every section.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
11

There's No Limit to How Bad Code Can Get

Why read thisReplacing a debt-heavy codebase from scratch can leave an organization maintaining two systems instead of one.

Summary available

Simon Willison September 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The evidence contains a strong chain of argument, though conditions for successful alternative rewrites are not developed in this example.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
12

How The Heck Does Shazam Work? (An Interactive Exploration)

Why read thisShazam-style recognition works by matching sparse frequency-and-timing landmarks, not melody, lyrics, or raw audio.

About 7 min · text estimate · Summary available

perthirtysix.com via Editor’s archive · Raindrop · Programming Digest May 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The evidence supports the technical explanation and interactive framing, but does not show the actual interactive widgets or visual quality.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
13

Your data model is your destiny

Why read thisA startup’s central data object can harden into product strategy, pricing, workflow, and defensibility.

Summary available

notes.mtb.xyz via Editor’s archive · Raindrop · Tech Manager Weekly November 2025
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The article uses business examples in the supplied text, but their historical accuracy was not independently checked.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
14

Code Yellow, Code Red

Why read thisCode Yellow and Code Red turn urgency into a temporary operating system with shared authority, transparency, and exit criteria.

Some background helpful · Summary available

The Engineering Manager July 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is a first-person organizational account; operational results are reported by the author and not independently checked here.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
15

The Agent Access Model

Why read thisAgent security may require shrinking, expiring authority per task run, because human-centered Zero Trust does not transfer cleanly to agents.

Technical reading · Summary available

Cloudflare Blog August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled but contains detailed model components, operational constraints, and explicit limits.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
16

Using anti-requirements to find system boundaries • Particular Software

Why read thisAbsurd fake rules between attributes can reveal whether business concepts truly belong together or sit in different model boundaries.

Some background helpful · Summary available

particular.net via Editor’s archive · Pocket
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence strongly supports the mechanism and examples, but does not show external validation or alternative modeling tradeoffs in depth.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
17

Beyond synthetic testing: Capturing and replaying real database workloads at Airbnb

Why read thisReal database traffic exposes upgrade risks that synthetic workloads miss, but useful replay requires preserving transactions, timing, and dependencies between queries.

Some background helpful · Summary available

airbnb.tech via Hungry Minds
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Operational results are self-reported, and several implementation sections require familiarity with database transactions and replay systems.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
18

Google - The Anatomy of a Large-Scale Hypertextual Web Search Engine, 1998

Why read thisBrin and Page argue web search needs authority, anchor text, context, and precision-first architecture, not merely larger document retrieval.

Some background helpful · Summary available

infolab.stanford.edu via Sachin Rekhi’s PM canon
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled from a technical paper, so some implementation sections and full argumentative flow are not visible.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
19

How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies

Why read thisClickbait weakens when feed retrieval shifts from cheap engagement proxies toward meaning, though each architecture pays a different operational price.

Some background helpful · Summary available

ByteByteGo August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The article says it relies on publicly shared sources; source quality and diagrams are not independently verifiable from the supplied evidence.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
20

Beyond happy path engineering: Time

Why read thisTime bugs start when one timestamp is forced to handle duration, ordering, expiry, scheduling, and business meaning.

Some background helpful · Summary available

blog.gaborkoos.com via Programming Digest August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, so the score cannot verify the article's complete structure, all examples, or whether later sections repeat or weaken the argument.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
21

How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache

Why read thisCloudflare saved cache memory by changing representation: removing duplicated, oversized, and scattered storage without changing DNS behavior.

Technical reading · Summary available

Cloudflare Blog August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Full evidence is available, but the subject is systems-heavy and may be less useful if the reader wants product or leadership material that day.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
22

CERN's migration path from CentOS Linux to Debian

Why read thisCERN’s Debian move turns on operational risk: newer CPU baselines could strand old accelerator-control hardware with narrow maintenance windows.

Some background helpful · Summary available

lwn.net via Lobsters September 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The text is sampled with gaps, so the complete presentation, visuals, and full treatment of counterarguments cannot be assessed.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
23

GraphRAG: How AI Answers Questions Hidden Across Many Documents

Why read thisGraphRAG targets questions whose answers emerge from corpus-wide relationships and patterns, not wording similarity to one retrievable passage.

Some background helpful · Summary available

ByteByteGo August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, and external references or benchmark claims were not independently checked.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
24

Does Code Quality Still Matter?

Why read thisTechnical debt may persist after human-readable code if machine-facing structures become costly for LLMs to change.

Brief pending · original available

blog.ploeh.dk via Ploeh Blog July 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The article is a speculative thought experiment, not an evidence-backed empirical analysis.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
25

How Stripe Built Kai: Data Dashboards, Reusable Skills, and Enterprise AI Governance

Why read thisEnterprise AI scales when one-off agent work becomes governed tool use, reusable workflow packaging, and policy-bound access to company data.

Summary available

chatprd.ai
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The text includes sponsor segments and episode promotion; all substantive material is relayed through an interview.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
26

A Tale of Two Flink Autoscalers

Why read thisNetflix’s Flink autoscaling shift moves from cluster-level symptoms to operator-level bottlenecks inside each job’s execution graph.

Technical reading · Summary available

Netflix Tech Blog August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is an excerpt with subscription/menu noise and sampled gaps, so full article depth cannot be fully verified.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
27

Trusting-Trust Attack against an Entire Linux Distribution (via the strip utility)

Why read thisA compromised `strip` utility can propagate a trusting-trust attack through a Linux distribution build.

Brief pending · original available

arxiv.org via Lobsters September 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Historical score; not verified under the current evidence-review process.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
28

How we could save petabytes of cache storage with Zstandard and Pingora

Why read thisCloudflare’s cache prototype pays compression once, then reuses smaller internal representations while keeping client-visible bytes unchanged for eligible text.

Summary available

Cloudflare Blog September 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The post reports a prototype and controlled tests, not a fully deployed fleet-wide outcome.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
29

Don’t stop early: Case-folding source code at memory speed

Why read thisCase folding is not lowercasing, and GitHub found branch-free full-buffer scanning can beat early exits at source-code scale.

Technical reading · Summary available

GitHub Blog July 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled and highly technical; personal accessibility is uncertain despite strong technical substance.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
30

Shopify replaced Redis with MySQL for inventory reservations–and it scaled

Why read thisHigh-throughput correctness came from changing the data shape, then discovering the binding constraint was connection ownership, not query speed.

Some background helpful · Summary available

shopify.engineering via Hacker News (100+ points) August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Historical score; not verified under the current evidence-review process.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
31

Why Engineers Should Invest in Decision Making Skills Early

Why read thisTechnical debates turn brittle when engineers skip goals and criteria, leaving hidden priorities to masquerade as solution preferences.

Summary available

Reforge December 2021
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, so completeness and full argumentative quality cannot be fully assessed.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
32

Writing a Fast Compiler

Why read thisFast compilation comes from doing less work and moving less data, with explicit tradeoffs in recovery, portability, and validation.

Technical reading · Summary available

tibleiz.net via Lobsters August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Full article text is available in evidence, but judgment is limited to its technical fit for this reader.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
33

Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp)

Why read thisWillison argues stateless MCP makes tool calls simpler, easier to scale, and more auditable by removing session management.

Technical reading · Summary available

Simon Willison August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. The article is partly a project/update note, so some value depends on interest in MCP implementation details.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
34

How modern browsers work

Why read thisBrowser performance becomes legible as dependent pipelines, where scripts, CSS, layout, compositing, and process isolation shape what users see.

Some background helpful · Summary available

Addy Osmani via Editor’s archive · Raindrop · Tech Manager Weekly September 2025
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, so depth, accuracy across the full article, diagrams, and absence of repetitive filler cannot be fully judged.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
35

EVE Online: The Move to Python 3 Begins!

Why read thisEVE Online’s Python 3 migration plan, including the scale of reviewing Python 2-to-3 behavior changes.

Brief pending · original available

Simon Willison August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Historical score; not verified under the current evidence-review process.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →
36

How and Why Netflix Built a Real-Time Distributed Graph: Part 3 — Querying the graph with gRPC…

Why read thisNetflix’s graph serving layer separates wide one-hop fan-out from deep dependent traversal, then plans execution around each pressure.

Technical reading · Summary available

Netflix Tech Blog August 2026
A personal relevance score

80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.

Evidence-reviewed score based on available publisher text. Evidence is an excerpt from a multi-part technical series, so the full implementation depth and later sections are not visible.

Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.

How scoring works →