Skip to content

What's New

Recently added and updated content β€” in reverse chronological order.


February 2026

Diagrams & Tooling

  • SVG Workflow Generation Best Practices β€” Mermaid-first, artifact-driven approach to producing committed SVG diagrams: diagram-as-code principles, repo conventions, style guide, CI-ready rendering workflow, and a full data platform example.

  • Mermaid β†’ SVG Workflow Pipeline (Tutorial) β€” Step-by-step guide to setting up @mermaid-js/mermaid-cli, rendering .mmd sources to .svg artifacts, and embedding them in MkDocs pages. Includes troubleshooting for font, viewBox, and Puppeteer issues.

  • Diagram Style Guide β€” When to use Mermaid vs SVG, diagram type selection by content, formatting conventions (orientation, subgraphs, node text limits), accessibility requirements, and a reusable Mermaid snippet library (control plane/data plane, pipeline stages, monolith vs microservices, MQTT broker, ML training vs serving).

  • ADR 0015: Standardize Diagrams on Mermaid β€” Mermaid becomes the site standard for architecture, flow, state, and sequence diagrams; SVG is reserved for geospatial illustrations and cases where Mermaid's layout engine is insufficient.

Site Doctrine & Structure

  • Start Here β€” Architectural Compass β€” Decision-tree navigation organized by problem domain: embedded systems, data pipelines, microservices, ML systems, geospatial, and infrastructure. Each path sequences 4–6 essays with context.

  • Reading Tracks β€” Six curated reading sequences: Modern Data Architecture, Distributed Systems & Scale, Embedded Systems Doctrine, Observability & Operations, Infrastructure Economics, and Spatial Systems.

  • Decision Frameworks β€” Aggregated decision frameworks from nine deep dives, each summarized in 5–10 lines: Kubernetes, Microservices, Serverless, Real-Time, Storage, Analytical Systems, Metadata Governance, ML Deployment, GPU Infrastructure, and Spatial Architecture.

  • Anti-Patterns Index β€” Six architectural anti-patterns with diagnostic signals and deep dive links: Premature Microservices, Overusing Kubernetes, Real-Time by Default, Data Swamp Formation, Serverless Cargo Cult, and Distributed Systems for Small Teams.

  • Philosophy of the Site β€” Five principles: Restraint Over Hype, Economics Over Fashion, Determinism Over Abstraction, Governance Over Chaos, Discipline Over Novelty.

  • Systems Thinking Glossary β€” Operationally-oriented definitions for: control plane, data plane, abstraction debt, blast radius, data gravity, eventual consistency, metadata debt, operational entropy, and schema contract.

  • ADR 0014: Elevate Site to Systems Doctrine β€” Structural decision to add reading tracks, decision frameworks, anti-patterns, philosophy, and glossary pages to transform the site into a navigable intellectual framework.

New Deep Dives

  • Why Most Kubernetes Clusters Shouldn't Exist β€” Orchestration overhead, etcd fragility, networking complexity, organizational maturity requirements, and the portability illusion. Decision matrix by team size and workload. (Themes: Infrastructure Β· Architecture Β· Economics)

  • The End of the Data Warehouse? β€” The warehouse is not dying β€” it is mutating. Lakehouse convergence, open table formats, DuckDB compute fragmentation, governance implications, and a tiered decision framework. (Themes: Data Architecture Β· Economics Β· Ecosystem)

  • The Economics of GPU Infrastructure β€” GPU scarcity, utilization patterns (~21% realistic vs 100% theoretical), CUDA/driver operational complexity, PCIe vs NVLink interconnect economics, training vs inference cost structures, and a buy-vs-rent decision matrix. (Themes: Infrastructure Β· Economics Β· ML Systems)

  • The Myth of Serverless Simplicity β€” Serverless relocates complexity rather than eliminating it. Cold starts, IAM explosion, observability fragmentation, vendor lock-in, and the economics of per-invocation billing at scale. (Themes: Infrastructure Β· Economics Β· Architecture)

  • Why Most ML Systems Fail in Production β€” Training/serving mismatch, data drift, feature skew, silent degradation, organizational misalignment, ML observability beyond accuracy metrics, and when heuristics are the right choice. (Themes: Data Architecture Β· Organizational Β· Economics)

  • The Physics of Storage Systems β€” HDD rotational latency through NVMe through cloud object storage. IO amplification, throughput vs IOPS, range requests, cold tiers, and a storage tier decision framework by workload type. (Themes: Storage Β· Infrastructure Β· Economics)

  • The Operational Geometry of Spatial Systems β€” Quadtree vs R-tree vs H3 hex grid indexing, COG vs GeoParquet format interaction, H3 partitioning strategies, routing graph vs raster cost surface trade-offs. (Themes: Spatial Β· Architecture Β· Data Formats)

  • The Hidden Cost of Metadata Debt β€” Catalog drift patterns, control plane collapse, governance vs bureaucracy, the economic cost of duplicate pipelines and compliance failure, and a progressive enforcement framework. (Themes: Governance Β· Data Architecture Β· Economics)

  • ADR 0012–0013: Deep Dive Scale Governance and Curation Model β€” Formal curation criteria (novelty, substance, durability, and non-tutorial tests), cluster soft maxima, cross-link requirements, and obsolescence handling for the now-29-essay Deep Dives corpus.

ASCII β†’ Mermaid Diagram Conversions

Converted ASCII diagrams in four deep dives to rendered Mermaid blocks:

  • Prefect vs Airflow β€” Airflow control plane / execution layer; Prefect API vs worker data plane separation
  • ESP32 vs Raspberry Pi β€” Side-by-side execution model stacks (bare-metal vs Linux kernel layers)
  • Why Most Data Pipelines Fail β€” Monolithic orchestration fan-out; DAG spaghetti coupling; shared warehouse coupling; event-driven chaos
  • Observability vs Monitoring β€” Sampling trade-off (100% / tail-1% / head-0.1%); data pipeline observability dimensions (freshness, completeness, correctness, lineage)

Recursive Cathedral Generator (Kotlin + Processing)

Late 2025

Mid 2025


Want to contribute or suggest content?

Open an issue or PR on GitHub. All content requests considered.