<?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 Murat Eksi</title><link>https://murateksi.com/tags/cloud-architecture/</link><description>Recent content in Cloud Architecture on Murat Eksi</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 10 Jul 2024 10:00:00 +0200</lastBuildDate><atom:link href="https://murateksi.com/tags/cloud-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Cloud Architecture Decisions Are Business Decisions</title><link>https://murateksi.com/posts/cloud-architecture-business-decisions/</link><pubDate>Wed, 10 Jul 2024 10:00:00 +0200</pubDate><guid>https://murateksi.com/posts/cloud-architecture-business-decisions/</guid><description>There is a persistent myth in technology organizations that architecture is a purely technical discipline, that decisions about service boundaries, data stores, and deployment strategies belong exclusively to engineers and should be surfaced to business leadership only after they&amp;rsquo;re made.
This is how organizations end up spending three years migrating a monolith to microservices while the market moved.
The cost of abstraction is a business question When a team chooses between a managed service and a self-hosted alternative, they are not evaluating technical trade-offs.</description></item></channel></rss>