---
title: "Discussion on \"Section C — Why On-Premise Became a Problem\" | Hashnode"
description: "Discussion on \"Section C — Why On-Premise Became a Problem\". In the previous section,\nwe learned how companies used to run their applications.\nThey bought:\n\nTheir own servers\nTheir own networking equipment\nTheir own storage\nTheir own cooling systems\nTheir own b"
url: "https://hashnode.com/posts/section-c-why-on-premise-became-a-problem/6a6778114bd125e22fbbf55f"
---

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

Discussion

# [Section C — Why On-Premise Became a Problem](https://backend-development-ashusnapx.hashnode.dev/section-c-why-on-premise-became-a-problem?utm_source=hashnode&utm_medium=feed)

In the previous section, we learned how companies used to run their applications. They bought: Their own servers Their own networking equipment Their own storage Their own cooling systems Their own b

Jul 27 · 5 min read · backend-development-ashusnapx.hashnode.dev  
Read the article

## Written by

[Ashutosh Kumar (Ashu)](https://hashnode.com/@ashusnapx)

@ashusnapx · San Francisco

  
[View profile](https://hashnode.com/@ashusnapx)

Generative AI Engineer. Production LLM apps: RAG, multi-agent workflows, MCP. Claude Certified Developer. ashusnapx.vercel.app

Generative AI Engineer. Production LLM apps: RAG, multi-agent workflows, MCP. Claude Certified Developer. ashusnapx.vercel.app

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
