Articles

Migration Demos

• Replacing a Python Service with Go, One Request at a Time

GraphQL Auth Explosion Case Study

The main spine: what went wrong in a distributed IAM-style system, why authorization checks multiplied, and how the implementation changed under real load.

• Start Here: From Scaffold to Scale
• Series Home
• Overview
• Part 1: Recursive SQL
• Part 2: Multiple Object Retrieval
• Part 3: Multiple Object Authorization
• Part 4: Redis Cache, per service
• Part 5: Smart APIs
• Part 6: GraphQL and Dataloader
• Conclusion: Architecture Is Throughput

Developer Affordances

Supporting notes about the tooling and implementation affordances that made the system fast enough to build, inspect, or stress. These are adjacent to the case study, but they are not numbered parts of the auth-explosion narrative.

• How I Scaffolded an Entire Distributed Platform in 10 Minutes
• ActiveResource and the Default Implementation that Astounded Me
• Explicit Authorization Contexts at the Model Boundary
• Extracting Cross-Service Models into Shared Gems
• Creating a Million Users
• Devcontainers for Local Distributed Systems
• Foreman for Local Process Orchestration

Engineering Essays

Standalone engineering arguments that do not depend on the IAM case study.

• Finer Points of Exception Handling
• The Database Doesn't Have to Look Like the Data