<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Call-Graph on Shaaf's blog</title><link>https://shaaf.dev/tags/call-graph/</link><description>Recent content in Call-Graph on Shaaf's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://shaaf.dev/tags/call-graph/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating an application to Quarkus: 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;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 migrating and using a tool like &lt;a href="https://github.com/sshaaf/rgctl">rgctl&lt;/a> which understands the codebase,
from a Graph POV and also understands its semnatically. It isnt a community detector only but puts emphasis on
mining the code details via Call graphs, dependenices, data flow in code, slicing, blast radius, harmonic centrality, betweeness and a little more of those things 😎.
rgctl takes one more step forward, using centraility, cfg etc, it creates migration hints. So one can choose the different ways to migrate and application.&lt;/p></description></item></channel></rss>