Architecture on Shaaf's blog

Enforcing Architecture with rgctl Policy Checks

Wed, 09 Sep 2026 00:00:00 +0000

Enforcing Architecture with rgctl Policy Checks

rgctl (Reachability Graph Control) indexes a codebase into a compact knowledge graph – functions, classes, calls, inheritance, communities – and serves deterministic, structured answers to questions about architecture, impact, and data flow. You run rgctl discover . once, and every subsequent query (blast-radius, metrics, gql) returns sub-millisecond results from the persisted graph. Agents and humans get the same exact facts. No re-reading source files, no confident guesses, no context window gymnastics.

Introducing rgctl: A Code Knowledge Graph for Engineering Teams and Agents

Mon, 07 Sep 2026 00:00:00 +0000

Introducing rgctl: A Code Knowledge Graph for Engineering Teams and Agents

Modern codebases are too large to hold in your head. They are also too large for most LLM context windows. When a coding agent needs to answer “what breaks if I change this function?” on a repository with 50,000 functions, its options are limited: grep through files, read a handful of them, and produce a confident answer that may be structurally wrong.

Decomposing a Monolith into Microservices with Call Graph Analysis

Tue, 01 Sep 2026 00:00:00 +0000

Decomposing a Monolith into Microservices with Call Graph Analysis

Splitting a monolith into microservices is a problem of finding boundaries. The wrong boundaries produce distributed monoliths – microservices that cannot be deployed independently because they call each other synchronously for every operation. The right boundaries follow natural seams in the code: clusters of functions that are tightly coupled internally but loosely connected to the rest of the system. This post picks up the CoolStore monolith from migrating it to Quarkus with rgctl and applies the same graph analysis to the next question: where to cut it into services.