<?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 Ilyas Hamdi</title><link>https://ilyashamdi.com/tags/architecture/</link><description>Recent content in Architecture on Ilyas Hamdi</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 04 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ilyashamdi.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Shaping architecture with SLOs</title><link>https://ilyashamdi.com/writing/slo-driven-infrastructure-architecture/</link><pubDate>Tue, 04 Mar 2025 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/slo-driven-infrastructure-architecture/</guid><description>SLO-driven architecture treats the SLO as upstream of the design. If your SLO has never caused you to ship later, it isn't doing the work.</description></item><item><title>The implicit architecture of every modernization decision</title><link>https://ilyashamdi.com/writing/implicit-architecture-modernization/</link><pubDate>Tue, 19 Nov 2024 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/implicit-architecture-modernization/</guid><description>Every modernization arrives with a stated goal and a much larger implicit one. The modernization that fails is the one where the implicit architecture was never named.</description></item><item><title>Infrastructure security architecture patterns</title><link>https://ilyashamdi.com/writing/infrastructure-security-architecture-patterns/</link><pubDate>Mon, 19 Aug 2024 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/infrastructure-security-architecture-patterns/</guid><description>A security pattern adopted without a threat model is a control with no clear job. The patterns aren't the problem. The application is.</description></item><item><title>What going containerized committed you to</title><link>https://ilyashamdi.com/writing/containerized-actual-commitment/</link><pubDate>Mon, 08 Apr 2024 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/containerized-actual-commitment/</guid><description>Containers were sold on consistency. The bill arrived in installments: orchestration, networking, security, observability. An honest audit of what the decision bought.</description></item><item><title>What a cloud architecture review should produce</title><link>https://ilyashamdi.com/writing/cloud-architecture-review-output/</link><pubDate>Thu, 26 Oct 2023 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/cloud-architecture-review-output/</guid><description>Most cloud architecture reviews produce a deck that gets filed. A useful review produces decisions framed for the people who can make them.</description></item><item><title>The architectural decisions hidden in a Dockerfile</title><link>https://ilyashamdi.com/writing/dockerfile-architectural-decisions/</link><pubDate>Tue, 21 Feb 2023 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/dockerfile-architectural-decisions/</guid><description>A Dockerfile is six lines and a dozen architectural commitments. Most teams write them by copy-paste. Few read them as decisions.</description></item><item><title>What technical leaders get wrong communicating architecture upward</title><link>https://ilyashamdi.com/writing/communicating-architecture-upward/</link><pubDate>Thu, 22 Sep 2022 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/communicating-architecture-upward/</guid><description>The same architecture decision can be approved by one audience and rejected by another in the same quarter. Which document each was reading is the difference.</description></item><item><title>What a cross-account migration forces you to confront</title><link>https://ilyashamdi.com/writing/cross-account-migration-confronts/</link><pubDate>Mon, 15 Aug 2022 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/cross-account-migration-confronts/</guid><description>A cross-account database move is the diagnostic, not the work. It surfaces architectural decisions you've been making implicitly for years.</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><item><title>The four kinds of cloud architecture debt</title><link>https://ilyashamdi.com/writing/cloud-architecture-debt/</link><pubDate>Tue, 19 Apr 2022 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/cloud-architecture-debt/</guid><description>Cloud architecture debt has four shapes: governance, operational, knowledge, optionality. Read the shape before you decide what to pay down.</description></item></channel></rss>