<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Ilyas Hamdi</title><link>https://ilyashamdi.com/tags/infrastructure/</link><description>Recent content in Infrastructure on Ilyas Hamdi</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 08 Dec 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://ilyashamdi.com/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>CI/CD pipeline architecture for infrastructure</title><link>https://ilyashamdi.com/writing/cicd-pipeline-architecture-infrastructure/</link><pubDate>Thu, 08 Dec 2022 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/cicd-pipeline-architecture-infrastructure/</guid><description>Application CI/CD is well-trodden. Infrastructure CI/CD is younger and stranger, and applying application patterns directly to it produces predictable failures.</description></item><item><title>IaC architecture at 5, 50, and 500 engineers</title><link>https://ilyashamdi.com/writing/iac-architecture-patterns/</link><pubDate>Tue, 14 Jun 2022 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/iac-architecture-patterns/</guid><description>The shape of your IaC architecture is downstream of team size. Most pain comes from running yesterday's architecture at today's scale.</description></item></channel></rss>