<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Svegile Engineering Blog</title>
    <link>https://www.svegile.com/blog</link>
    <description>Engineering writing from the Svegile team on AI agents, cloud migrations, APIs, observability, and operating software after launch.</description>
    <language>en</language>
    <lastBuildDate>Wed, 29 Apr 2026 08:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.svegile.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Blue-Green vs. Canary vs. Rolling Deployments</title>
      <link>https://www.svegile.com/blog/blue-green-vs-canary-vs-rolling-deployments</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/blue-green-vs-canary-vs-rolling-deployments</guid>
      <pubDate>Wed, 29 Apr 2026 08:00:00 +0000</pubDate>
      <description>There is no universally correct deployment strategy. The right choice depends on rollback speed, observability maturity, coexistence risk, and budget.</description>
    </item>
    <item>
      <title>Batch vs. Streaming in AI Pipelines: When Latency Actually Matters</title>
      <link>https://www.svegile.com/blog/batch-vs-streaming-in-ai-pipelines-when-latency-actually-matters</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/batch-vs-streaming-in-ai-pipelines-when-latency-actually-matters</guid>
      <pubDate>Mon, 20 Apr 2026 08:00:00 +0000</pubDate>
      <description>Stop rebuilding batch pipelines as streaming because someone said real-time everything. The real question is where lower latency creates measurable value.</description>
    </item>
    <item>
      <title>AWS Well-Architected Framework in Practice: Lessons from Real Migration Projects</title>
      <link>https://www.svegile.com/blog/aws-well-architected-framework-lessons-from-real-migration-projects</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/aws-well-architected-framework-lessons-from-real-migration-projects</guid>
      <pubDate>Tue, 14 Apr 2026 08:00:00 +0000</pubDate>
      <description>The Well-Architected Framework is a diagnostic conversation, not a certification. Its value comes from honest answers about migration risk, not green reports.</description>
    </item>
    <item>
      <title>Automating Document Processing Pipelines with OCR, Classification, and Validation</title>
      <link>https://www.svegile.com/blog/automating-document-processing-pipelines-ocr-classification-validation</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/automating-document-processing-pipelines-ocr-classification-validation</guid>
      <pubDate>Sun, 05 Apr 2026 08:00:00 +0000</pubDate>
      <description>Stop building monolithic document processing systems. The durable pattern is a layered pipeline with OCR, classification, validation, and confidence routing.</description>
    </item>
    <item>
      <title>Non-breaking usually means additive</title>
      <link>https://www.svegile.com/blog/api-versioning-strategies-that-do-not-break-existing-clients</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/api-versioning-strategies-that-do-not-break-existing-clients</guid>
      <pubDate>Fri, 27 Mar 2026 08:00:00 +0000</pubDate>
      <description>Most teams still break consumers and treat deprecation as an afterthought. Versioning is how you keep the API promise.</description>
    </item>
    <item>
      <title>API Gateway Patterns: Authentication, Routing, and Transformation at the Edge</title>
      <link>https://www.svegile.com/blog/api-gateway-patterns-authentication-routing-transformation-edge</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/api-gateway-patterns-authentication-routing-transformation-edge</guid>
      <pubDate>Wed, 18 Mar 2026 08:00:00 +0000</pubDate>
      <description>Authentication, routing, and transformation belong at the gateway: centralizing them removes inconsistency, shrinks the security surface, and frees services.</description>
    </item>
    <item>
      <title>Anatomy of a Production AI Agent: Memory, Tools, Guardrails, and Fallbacks</title>
      <link>https://www.svegile.com/blog/anatomy-of-a-production-ai-agent-memory-tools-guardrails-fallbacks</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/anatomy-of-a-production-ai-agent-memory-tools-guardrails-fallbacks</guid>
      <pubDate>Fri, 06 Mar 2026 08:00:00 +0000</pubDate>
      <description>A demo agent chains a model to a tool. A production agent survives failing APIs, policy limits, and messy workflows thanks to the subsystems around it.</description>
    </item>
    <item>
      <title>Alert Fatigue: Designing Alerting Rules That Get Acknowledged, Not Ignored</title>
      <link>https://www.svegile.com/blog/alert-fatigue-designing-alerting-rules-that-get-acknowledged</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/alert-fatigue-designing-alerting-rules-that-get-acknowledged</guid>
      <pubDate>Sat, 28 Feb 2026 08:00:00 +0000</pubDate>
      <description>Alert fatigue starts when teams page on internal noise instead of real user pain. Better alerting starts with symptoms, SLO burn rates, and ruthless pruning.</description>
    </item>
    <item>
      <title>Agent Observability: Tracing Multi-Step Reasoning in Production</title>
      <link>https://www.svegile.com/blog/agent-observability-tracing-multi-step-reasoning</link>
      <guid isPermaLink="true">https://www.svegile.com/blog/agent-observability-tracing-multi-step-reasoning</guid>
      <pubDate>Thu, 12 Feb 2026 08:00:00 +0000</pubDate>
      <description>Agent observability is the difference between shipping AI agents and understanding why they fail, loop, or overspend in production.</description>
    </item>
  </channel>
</rss>
