<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Axum on Gaurav.dev</title><link>/tags/axum/</link><description>Recent content in Axum on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/axum/index.xml" rel="self" type="application/rss+xml"/><item><title>Fiber or Axum for Performance-Critical Services?</title><link>/posts/fiber-axum-performance-services/</link><pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate><guid>/posts/fiber-axum-performance-services/</guid><description>&lt;p&gt;Go and Rust are compelling when a service has demanding latency, throughput, memory, or reliability constraints. Fiber and Axum provide productive HTTP layers for those ecosystems, but choosing between them is a broader decision than comparing router benchmarks.&lt;/p&gt;&#10;&lt;h2 id="fiber-operational-simplicity-with-go"&gt;Fiber: operational simplicity with Go&lt;/h2&gt;&#10;&lt;p&gt;Fiber offers an Express-inspired API on top of Go’s &lt;code&gt;fasthttp&lt;/code&gt; ecosystem. Teams coming from JavaScript can become productive quickly, while Go provides straightforward compilation, deployment, concurrency, and tooling. A single binary with predictable runtime behaviour is valuable for containers, edge nodes, and operationally lean teams.&lt;/p&gt;</description></item></channel></rss>