{
  "id": 7956093,
  "title": "Ten years building applications, zero years designing infrastructure. Starting AWS in public.",
  "url": "https://urgent.news/2026/09/17/ten-years-building-applications-zero-years-designing-infrastructure",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-17T05:05:54.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/tayyabhassan04/ten-years-building-applications-zero-years-designing-infrastructure-starting-aws-in-public-b0j"
  },
  "original_language": "en",
  "account": "For a decade, the author has been coding professionally, building a complex ERP system and managing the infrastructure behind it. However, they realize that their hands-on experience has left them unprepared for the actual challenges of infrastructure design.\n\nThe ERP system, consisting of 17 modules, has been running smoothly for a year with no complaints. Yet, upon drawing a proper architecture diagram, the author discovers two critical issues. First, all modules rely on a single server, meaning a server failure would bring down the entire system. Second, the reporting module generates reports synchronously, causing significant slowdown when multiple users attempt to generate reports simultaneously.\n\nThe author's limited experience with infrastructure spans only one machine, one database, and one environment. They lack knowledge of multi-availability zones, message queues, and infrastructure as code. While they understand DNS and networking to some extent, they recognize that these are distinct skills.\n\nTo address these gaps, the author plans to study for the AWS Solutions Architect Associate certification and migrate parts of the ERP to AWS. Their first project will be to decouple the report generation process from the request path, moving it to a queue for processing by workers. This change will prevent the entire system from grinding to a halt when generating reports.\n\nThe author commits to documenting their journey over the next twelve months, sharing the challenges they face and the lessons they learn. By being transparent about their mistakes and setbacks, they hope to provide valuable insights for others making the transition from application development to infrastructure design.",
  "summary": "I have been writing code professionally for ten years. React, Node, PostgreSQL, PHP before that. I have shipped a 17-module ERP that 100 people use every day to run a business. I manage the servers it runs on, the DNS, the hosting, the deploys. Until a few weeks ago I thought that meant I understood infrastructure. It does not. What it means is that I have been very good at keeping one machine…",
  "key_points": [],
  "editors_take": null,
  "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."
}