<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rust on Shaaf's blog</title><link>https://shaaf.dev/tags/rust/</link><description>Recent content in Rust on Shaaf's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://shaaf.dev/tags/rust/index.xml" rel="self" type="application/rss+xml"/><item><title>Enforcing Architecture with rgctl Policy Checks</title><link>https://shaaf.dev/post/2026-09-09-enforcing-architecture-with-rgctl-policy-checks/</link><pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/2026-09-09-enforcing-architecture-with-rgctl-policy-checks/</guid><description>&lt;h1 id="enforcing-architecture-with-rgctl-policy-checks">Enforcing Architecture with rgctl Policy Checks&lt;/h1>
&lt;p>&lt;a href="https://github.com/sshaaf/rgctl">rgctl&lt;/a> (Reachability Graph Control) indexes a codebase into a compact knowledge graph &amp;ndash; functions, classes, calls, inheritance, communities &amp;ndash; and serves deterministic, structured answers to questions about architecture, impact, and data flow. You run &lt;code>rgctl discover .&lt;/code> once, and every subsequent query (&lt;code>blast-radius&lt;/code>, &lt;code>metrics&lt;/code>, &lt;code>gql&lt;/code>) 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.&lt;/p></description></item><item><title>Introducing rgctl: A Code Knowledge Graph for Engineering Teams and Agents</title><link>https://shaaf.dev/post/2026-09-07-introducing-rgctl-a-code-knowledge-graph-for-engineering-teams-and-agents/</link><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/2026-09-07-introducing-rgctl-a-code-knowledge-graph-for-engineering-teams-and-agents/</guid><description>&lt;h1 id="introducing-rgctl-a-code-knowledge-graph-for-engineering-teams-and-agents">Introducing rgctl: A Code Knowledge Graph for Engineering Teams and Agents&lt;/h1>
&lt;p>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 &amp;ldquo;what breaks if I change this function?&amp;rdquo; 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.&lt;/p></description></item><item><title>Decomposing a Monolith into Microservices with Call Graph Analysis</title><link>https://shaaf.dev/post/decomposing-a-monolith-into-microservices-with-call-graph-analysis/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/decomposing-a-monolith-into-microservices-with-call-graph-analysis/</guid><description>&lt;h1 id="decomposing-a-monolith-into-microservices-with-call-graph-analysis">Decomposing a Monolith into Microservices with Call Graph Analysis&lt;/h1>
&lt;p>Splitting a monolith into microservices is a problem of finding boundaries. The
wrong boundaries produce distributed monoliths &amp;ndash; 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
&lt;a href="https://shaaf.dev/post/migrating-coolstore-monolith-to-quarkus-with-rgctl/">migrating it to Quarkus with rgctl&lt;/a>
and applies the same graph analysis to the next question: where to cut it into
services.&lt;/p></description></item><item><title>Application Migration using A Graph-Driven Approach with rgctl</title><link>https://shaaf.dev/post/migrating-coolstore-monolith-to-quarkus-with-rgctl/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/migrating-coolstore-monolith-to-quarkus-with-rgctl/</guid><description>&lt;h1 id="application-migration-using-a-graph-driven-approach-with-rgctl">Application Migration using A Graph-Driven Approach with rgctl&lt;/h1>
&lt;p>Migrating an application takes a lot of time and energy, which itself is on a collision course
with complexity in codebases. Leaving aside the discussion on people and process. In this blog post
I would like to highlight the journey of migration and using a tool like &lt;strong>Reachability Graph Control&lt;/strong> - &lt;a href="https://github.com/sshaaf/rgctl">rgctl&lt;/a> which understands the codebase. Although I have taken an example of Java, the tool supports &lt;a href="https://shaaf.dev/rgctl/docs/languages/">multiple languages&lt;/a> like C, C#, Go, Node etc.&lt;/p></description></item><item><title>Adding Rust Support and Some Major updates to My Neovim Config</title><link>https://shaaf.dev/post/2026-03-09-neovim-rust-update/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/2026-03-09-neovim-rust-update/</guid><description>&lt;p>It&amp;rsquo;s been about 8 months since my &lt;a href="https://shaaf.dev/post/2025-07-17-neovim4java/">last update on neovim4j&lt;/a>, and the config has evolved significantly. The name &amp;ldquo;neovim4j&amp;rdquo; is now a bit of a misnomer—while it started as a Java-focused setup, it&amp;rsquo;s grown into a polyglot development environment.&lt;/p>
&lt;h2 id="rust-support-">Rust Support 🦀&lt;/h2>
&lt;p>The biggest addition is comprehensive &lt;strong>Rust support&lt;/strong>. I&amp;rsquo;ve integrated:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>rustaceanvim&lt;/strong> for advanced LSP features powered by rust-analyzer&lt;/li>
&lt;li>&lt;strong>crates.nvim&lt;/strong> for smart Cargo.toml management and dependency completion&lt;/li>
&lt;li>&lt;strong>codelldb&lt;/strong> debugger integration&lt;/li>
&lt;li>&lt;strong>neotest&lt;/strong> for running Rust tests directly in the editor&lt;/li>
&lt;/ul>
&lt;p>The Rust setup mirrors the Java tooling quality—full LSP, debugging, and testing all working seamlessly. Semantic highlighting is disabled in favor of Treesitter for more colorful syntax highlighting.&lt;/p></description></item><item><title>My first 6 hours with Rust</title><link>https://shaaf.dev/post/my-first-6-hours-with-rust/</link><pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/my-first-6-hours-with-rust/</guid><description>&lt;p>&lt;strong>TLDR&lt;/strong>; I took a day off from work today, although still most of my time I ended up doing my travel expenses. Talk about priorities. I am the one to blame here totally. 😄&lt;/p>
&lt;p>So come around lunch time, thats when all the fluids are ready to do something different. I ended up exploring some basics about Rust. I heard a friend once said, if a prominent person (wonder who that is..) says billions over and over again, somehow people just start believing in billions. Anyways I am totally sold by my youtube feed to explore this a bit. What is this rust thing? And before I go any further, just to let you know I like programming languages and problem solving. I am not hung up on one language. I appreciate them all. Except MS access (oops)&lt;/p></description></item></channel></rss>