{
  "id": 20891451,
  "title": "Cloud Infrastructure for Your First Stack: Components, Costs and a Decision Tree",
  "url": "https://urgent.news/2026/11/20/cloud-infrastructure-for-your-first-stack-components-costs-and-a",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-20T11:32:32.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/nilesharma0108/cloud-infrastructure-for-your-first-stack-components-costs-and-a-decision-tree-51pb"
  },
  "original_language": "en",
  "account": "Cloud infrastructure is a collection of physical and virtual resources provided by cloud providers through the internet. These resources include compute, storage, networking, databases, and security controls. Users create and manage these resources using web consoles, command-line tools, or APIs, without direct access to the underlying hardware. Cloud infrastructure differs from traditional server ownership in that it is on-demand, pay-as-you-go, and elastic, allowing users to scale resources up or down based on their needs.\n\nThe core components of cloud infrastructure are:\n\n1. Compute: Processors for running code, available as virtual machines (VMs), containers, or serverless functions.\n2. Storage: Keeps files and data, available as object storage, block storage, and file storage.\n3. Networking: Connects all components and allows external access, including virtual private networks, firewalls, load balancers, DNS, and public IP addresses.\n4. Databases: Managed or self-managed solutions for storing and organizing data, such as Amazon RDS, Google Cloud SQL, Azure SQL Database, or managed PostgreSQL like Supabase.\n5. Content Delivery Network (CDN): Stores copies of static files (images, CSS, JavaScript, and whole pages) on servers worldwide for faster user downloads.\n6. Identity and Access Management (IAM): Controls who and what can perform actions within an account, including team members, apps, storage buckets, and API keys.\n\nCloud infrastructure services are often categorized by the level of management provided by the provider:\n\n1. Infrastructure as a Service (IaaS): Users manage operating systems, applications, and data themselves, while the provider handles the underlying hardware and infrastructure.\n2. Platform as a Service (PaaS): Users manage applications and data, while the provider handles the platform, including operating systems, middleware, and development tools.\n3. Serverless: Users focus solely on writing and deploying code, with the provider managing the infrastructure, scaling, and server management.\n4. Managed platforms: Users manage applications and data, while the provider handles the platform, including operating systems, middleware, development tools, and basic infrastructure management.\n\nWhen building a first real project, engineers typically face questions about choosing the appropriate cloud infrastructure model, understanding billing components such as egress, public IPv4, and idle resources, and managing operating system and identity and access management (IAM) tasks. Factors such as egress costs, public IPv4 usage, and idle resources can significantly impact the overall cost of running a project in the cloud. Additionally, the level of control required in terms of OS and IAM management varies depending on the chosen service model.",
  "summary": "Choosing where to run a first real project usually comes down to a few engineering questions: VPS, serverless, a managed platform or a full hyperscaler; how egress, public IPv4 and idle resources show up on the bill; and how much of the OS and IAM work lands on you. Below are the six building blocks, the service models side by side, starting prices for AWS, Google Cloud, Azure, Vercel,…",
  "key_points": [
    "Cloud infrastructure includes compute, storage, networking, databases, and security controls.",
    "Service models: IaaS, PaaS, serverless, and managed platforms with varying levels of control."
  ],
  "editors_take": "Selecting a service model forces engineers to balance the desire for granular control over operating systems against the necessity of managing unpredictable costs from egress and idle resources.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}