<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Shubham Srivastava</title><link>https://shubhamsrivastava.co.in/tags/architecture/</link><description>Recent content in Architecture on Shubham Srivastava</description><image><title>Shubham Srivastava</title><url>https://shubhamsrivastava.co.in/images/home.png</url><link>https://shubhamsrivastava.co.in/images/home.png</link></image><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright © 2024, Shubham Srivastava.</copyright><lastBuildDate>Mon, 20 Apr 2026 15:40:00 +0530</lastBuildDate><atom:link href="https://shubhamsrivastava.co.in/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Retries, Timeouts, and Idempotency: The Trio That Defines Production Reliability</title><link>https://shubhamsrivastava.co.in/blog/retries-timeouts-and-idempotency-the-trio-that-defines-production-reliability/</link><pubDate>Mon, 20 Apr 2026 15:40:00 +0530</pubDate><guid>https://shubhamsrivastava.co.in/blog/retries-timeouts-and-idempotency-the-trio-that-defines-production-reliability/</guid><description>Why retries, timeouts, and idempotency are not implementation details but core design choices that define reliability in distributed systems.</description></item><item><title>The Death of the 'Prompt Engineer,' the Rise of the 'Agent Architect'</title><link>https://shubhamsrivastava.co.in/blog/death-of-prompt-engineer/</link><pubDate>Sun, 29 Mar 2026 18:15:49 +0530</pubDate><guid>https://shubhamsrivastava.co.in/blog/death-of-prompt-engineer/</guid><description>Witnessing the fundamental shift from Prompt Engineering to Agentic Workflows and Agent Architectures.</description></item><item><title>The Cost of Missing Context: Why I Built Crumbs</title><link>https://shubhamsrivastava.co.in/projects/crumbs/</link><pubDate>Sun, 17 Aug 2025 00:00:00 +0000</pubDate><guid>https://shubhamsrivastava.co.in/projects/crumbs/</guid><description>Error handling in Go is intentionally simple, but in large-scale distributed systems, simplicity without context is a liability. Here is how Crumbs fixes that.</description></item><item><title>Neon: A Lightweight, Zero-Dependency Go HTTP Framework</title><link>https://shubhamsrivastava.co.in/projects/neon/</link><pubDate>Sat, 13 Jan 2024 10:45:43 +0530</pubDate><guid>https://shubhamsrivastava.co.in/projects/neon/</guid><description>The Pursuit of Minimalism in Go Web APIs - Building a high-velocity developer experience without the dependency tree.</description></item></channel></rss>