<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloud Architecture on Saurabh Chaubey</title>
    <link>https://saurabh-chaubey.com/tags/cloud-architecture/</link>
    <description>Recent content in Cloud Architecture on Saurabh Chaubey</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 20 Mar 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://saurabh-chaubey.com/tags/cloud-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Terraform Modules as Contracts: Designing Interfaces That Work Across Any Environment</title>
      <link>https://saurabh-chaubey.com/post/devops/terraform-modules-as-contracts-designing-interfaces/</link>
      <pubDate>Fri, 20 Mar 2026 10:00:00 +0000</pubDate>
      
      <guid>https://saurabh-chaubey.com/post/devops/terraform-modules-as-contracts-designing-interfaces/</guid>
      <description>Stop designing modules around cloud APIs. Start designing them around what your team actually needs to say.
Here&amp;rsquo;s a question: when you add a new environment to your Terraform project, how much code do you touch?
If the answer involves editing module internals, adding if statements, or copying resource blocks — your module boundaries are in the wrong place. A well-designed Terraform module should work like a contract. The consumer says what they want.</description>
    </item>
    
  </channel>
</rss>
