---
title: "Discussion on \"The Cloud Exit Strategy: Architecting for Independence\" | Hashnode"
description: "Discussion on \"The Cloud Exit Strategy: Architecting for Independence\". We have normalized a dangerous standard in modern web development: paying hundreds of dollars a month for infrastructure before acquiring a single customer. We build distributed systems for simple problems. We rent our identity, our data, and our com..."
url: "https://hashnode.com/posts/the-cloud-exit-strategy-architecting-for-independence/696f61cc936cf0a3546bfbea"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Cloud Exit Strategy: Architecting for Independence](https://zoo.hashnode.dev/the-cloud-exit-strategy-architecting-for-independence?utm_source=hashnode&utm_medium=feed)

We have normalized a dangerous standard in modern web development: paying hundreds of dollars a month for infrastructure before acquiring a single customer. We build distributed systems for simple problems. We rent our identity, our data, and our com...

Jan 20 · 5 min read · zoo.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#engineering](https://hashnode.com/tag/engineering)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)
-   [#self-hosted](https://hashnode.com/tag/self-hosted)
-   [#architecture](https://hashnode.com/tag/architecture)

## Written by

[KEN MWAURA](https://hashnode.com/@Zoo-Codes)

@Zoo-Codes · Nairobi , Kenya

  
[View profile](https://hashnode.com/@Zoo-Codes)

Software Engineer

Nairobi, Kenya

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
