https://thenewstack.io/technical-debt-vs-architecture-debt-dont-confuse-them/ TNS OK SUBSCRIBE Join our community of software engineering leaders and aspirational developers. Always stay in-the-know by getting the most important news and exclusive content delivered fresh to your inbox to learn more about at-scale software development. EMAIL ADDRESS REQUIRED [ ] SUBSCRIBE RESUBSCRIPTION REQUIRED It seems that you've previously unsubscribed from our newsletter in the past. Click the button below to open the re-subscribe form in a new tab. When you're done, simply close that tab and continue with this form to complete your subscription. RE-SUBSCRIBE The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our Terms of Use and Privacy Policy. Welcome and thank you for joining The New Stack community! Please answer a few simple questions to help us deliver the news and resources you are interested in. FIRST NAME REQUIRED [ ] LAST NAME REQUIRED [ ] COMPANY NAME REQUIRED [ ] COUNTRY REQUIRED [Select ... ] ZIPCODE REQUIRED [ ] Great to meet you! Tell us a bit about your job so we can cover the topics you find most relevant. What is your job level? REQUIRED [Select ... ] [ ] Which of these most closely describes your job role? REQUIRED [Select ... ] [ ] How many employees are in the organization you work with? REQUIRED [Select ... ] What option best describes the type of organization you work for? REQUIRED [Select ... ] [ ] Which of the following best describes your organization's primary industry? REQUIRED [Select ... ] [ ] LINKEDIN PROFILE URL [ ] Welcome! We're so glad you're here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game. What's next? Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups. Follow TNS on your favorite social media networks. Become a TNS follower on LinkedIn. Check out the latest featured and trending stories while you wait for your first TNS newsletter. PREV 1 of 2 NEXT VOXPOP As a JavaScript developer, what non-React tools do you use most often? Angular 0% Astro 0% Svelte 0% Vue.js 0% Other 0% I only use React 0% I don't use JavaScript 0% Thanks for your opinion! Subscribe below to get the final results, published exclusively in our TNS Update newsletter: [ ] SUBMIT NEW! Try Stackie AI ARCHITECTURE Cloud Native Ecosystem Containers Databases Edge Computing Infrastructure as Code Linux Microservices Open Source Networking Storage ENGINEERING AI AI Engineering API Management Backend development Data Frontend Development Large Language Models Security Software Development WebAssembly OPERATIONS AI Operations CI/CD Cloud Services DevOps Kubernetes Observability Operations Platform Engineering PROGRAMMING C++ Developer tools Go Java JavaScript Programming Languages Python Rust TypeScript CHANNELS Podcasts Ebooks Events Webinars Newsletter TNS RSS Feeds THE NEW STACK About / Contact Sponsors Advertise With Us Contributions PODCASTS EBOOKS EVENTS WEBINARS NEWSLETTER CONTRIBUTE ARCHITECTURE ENGINEERING OPERATIONS PROGRAMMING Cloud Native Ecosystem Containers Databases Edge Computing Infrastructure as Code Linux Microservices Open Source Networking Storage Can the 50-Year-Old Actor Model Rescue Agentic AI? Oct 22nd 2025 7:47am, by Kimberley Mok OpenSearch 3.3's New AI Agents Now Generally Available for Developers Oct 16th 2025 12:00pm, by Steven J. Vaughan-Nichols Crossing the AI Chasm: Lessons From the Early Days of Cloud Oct 9th 2025 7:00am, by Randy Bias OpenStack Flamingo Reduces Technical Debt, Boosts Performance Oct 7th 2025 11:00am, by Steven J. Vaughan-Nichols Broadcom Ends Free Bitnami Images, Forcing Users To Find Alternatives Sep 30th 2025 8:00am, by Joab Jackson How To Deploy a Local AI via Docker Oct 23rd 2025 11:00am, by Jack Wallen Are Unikernels the Answer for Next-Gen AI Cloud Workloads? Oct 23rd 2025 7:00am, by Joab Jackson How To Get Bare-Metal GPU Performance in Confidential VMs Oct 21st 2025 4:00am, by Steven J. Vaughan-Nichols Why Modern IPv6 Failed This Massive Kubernetes Networking Test Oct 20th 2025 12:00pm, by Steven J. Vaughan-Nichols How to Quickly Deploy GitLab via Docker Oct 15th 2025 9:00am, by Jack Wallen 2 Fixes Vastly Cut TiKV Write Stalls From SST File Ingestion Oct 24th 2025 11:00am, by Jinpeng Zhang Breaking the 'Shared-Nothing' Bottleneck: A NoSQL Paradigm Oct 23rd 2025 8:00am, by Carol Platz OpenSearch 3.3's New AI Agents Now Generally Available for Developers Oct 16th 2025 12:00pm, by Steven J. Vaughan-Nichols Search Isn't Dead: From RAG to Agents With Vector Databases Oct 16th 2025 10:30am, by Vicki Walker A Taste of P99 CONF: Low Latency With eBPF, Rust and More Oct 14th 2025 8:30am, by Cynthia Dunlop Right-Sizing AI for the Edge: Power, Models and Security Oct 9th 2025 10:00am, by Chris J. Preimesberger Why the Edge Isn't Just 'Cloud Computing, But Closer' Sep 16th 2025 9:00am, by Charles Humble Kubernetes at the Edge: Deploy With Confidence and Control Aug 19th 2025 10:00am, by Vicki Walker Scaling AI Inference at the Edge With Distributed PostgreSQL Jul 21st 2025 9:00am, by Meredith Shubel 6 Design Principles for Edge Computing Systems Jul 17th 2025 7:00am, by Joab Jackson Project infragraph: IBM's Real-Time Model for Infrastructure Assets Sep 26th 2025 4:00am, by Joab Jackson Chef Creator Unveils AI Platform To Fix Flaws With Infrastructure Automation Aug 27th 2025 8:00am, by Heather Joslyn Platform Engineering Is Failing -- Here's Why Infrastructure Comes First Aug 7th 2025 10:00am, by Lukas Gentele How To Use AI To Design Intelligent, Adaptable Infrastructure Aug 1st 2025 10:00am, by Dharani Pothula Software Architecture Is Finally Fixing Its Biggest Problem: Developer Experience Jul 25th 2025 9:00am, by Avraam Tolmidis Are Unikernels the Answer for Next-Gen AI Cloud Workloads? Oct 23rd 2025 7:00am, by Joab Jackson Why Broadcom's Ubuntu Bet on VMware Will Delight Devs and Ops Oct 14th 2025 1:00pm, by B. Cameron Gain Run Containers and VMs Easily With OrbStack GUI Oct 10th 2025 8:00am, by Jack Wallen SysLinuxOS: The Go-To Linux for System Administrators Oct 5th 2025 7:00am, by Jack Wallen Is Oreon Linux a True Red Hat Enterprise Alternative? Sep 21st 2025 7:00am, by Jack Wallen How Dapr and WebAssembly Team Up for Microservices Oct 2nd 2025 6:00am, by B. Cameron Gain Your CI/CD Pipeline Wasn't Built for Microservices Aug 7th 2025 7:00am, by Arjun Iyer Introduction to Microservices Aug 5th 2025 5:00pm, by TNS Staff FoundationDB: A Distributed Database That Can't Be Killed Jul 25th 2025 7:00am, by Joab Jackson Why Scaling Makes Microservices Testing Exponentially Harder Jul 16th 2025 11:00am, by Arjun Iyer How TARmageddon Compromises Rust Security: A Developer's Guide Oct 24th 2025 10:00am, by Steven J. Vaughan-Nichols React Native Rolls Out Its Latest Version on New Architecture Oct 18th 2025 7:00am, by Loraine Lawson OpenSearch 3.3's New AI Agents Now Generally Available for Developers Oct 16th 2025 12:00pm, by Steven J. Vaughan-Nichols Kubernetes: From a Federation of Bazaars to the AI Frontier Oct 13th 2025 10:00am, by Antonio Ojea Everything Big Starts Small: Building Open Social Web Apps Oct 9th 2025 11:00am, by Richard MacManus How To Deploy a Local AI via Docker Oct 23rd 2025 11:00am, by Jack Wallen Breaking the 'Shared-Nothing' Bottleneck: A NoSQL Paradigm Oct 23rd 2025 8:00am, by Carol Platz Why Modern IPv6 Failed This Massive Kubernetes Networking Test Oct 20th 2025 12:00pm, by Steven J. Vaughan-Nichols How to Quickly Deploy GitLab via Docker Oct 15th 2025 9:00am, by Jack Wallen Leaner, More Efficient Storage Infrastructure for the AI Era Oct 8th 2025 11:42am, by Carol Platz 2 Fixes Vastly Cut TiKV Write Stalls From SST File Ingestion Oct 24th 2025 11:00am, by Jinpeng Zhang Breaking the 'Shared-Nothing' Bottleneck: A NoSQL Paradigm Oct 23rd 2025 8:00am, by Carol Platz Building a Self-Aware Enterprise With GenAI Oct 21st 2025 7:00am, by Ed Huang Vert Is a File Format Converter You Can Quickly Deploy With Docker Oct 19th 2025 7:00am, by Jack Wallen A Taste of P99 CONF: Low Latency With eBPF, Rust and More Oct 14th 2025 8:30am, by Cynthia Dunlop AI AI Engineering API Management Backend development Data Frontend Development Large Language Models Security Software Development WebAssembly IBM's Mellea Tackles Open Source AI's Hidden Weakness Oct 24th 2025 3:00pm, by Darryl K. Taft How MIT's Project NANDA Aims To Decentralize AI Agents Oct 24th 2025 8:00am, by Richard MacManus Securing the Vibe: Reducing the Risk of AI-Generated Code Oct 24th 2025 5:24am, by Crystal Morin Why Kubernetes Security Is Critical for GenAI Integrity Oct 23rd 2025 2:00pm, by Utpal Bhatt How OpenAI's AgentKit Embeds ChatGPT Into Any Website Oct 23rd 2025 12:03pm, by Janakiram MSV IBM's Mellea Tackles Open Source AI's Hidden Weakness Oct 24th 2025 3:00pm, by Darryl K. Taft Securing the Vibe: Reducing the Risk of AI-Generated Code Oct 24th 2025 5:24am, by Crystal Morin An Ethics Crash Course for Agentic AI: Autonomy Versus Trust Oct 22nd 2025 5:05am, by Vrushali Sawant and Manisha Khanna As Vibe Coding Fades, Woz Offers Production-Ready Alternative Oct 21st 2025 3:00pm, by Darryl K. Taft Building a Self-Aware Enterprise With GenAI Oct 21st 2025 7:00am, by Ed Huang MCP vs. API Gateways: They're Not Interchangeable Oct 20th 2025 8:00am, by Christian Posta React Native Rolls Out Its Latest Version on New Architecture Oct 18th 2025 7:00am, by Loraine Lawson The Modern APIs Roundtable: How AI Creates New Challenges for API Security Oct 15th 2025 11:00am, by Adam LaGreca Kong Releases Volcano, an MCP-Native SDK for Building AI Agents Oct 15th 2025 10:00am, by Loraine Lawson How You.com Survived ChatGPT With a Pivot to Enterprise AI Oct 3rd 2025 7:00am, by Richard MacManus Vibe Coding: When AI Writes the Code, Who Secures It? Sep 26th 2025 1:00pm, by Crystal Morin How MCP Uses Streamable HTTP for Real-Time AI Tool Interaction Aug 18th 2025 10:34am, by Janakiram MSV A Backend for Frontend: Watt for Node.js Simplifies Operations Aug 14th 2025 6:00am, by Loraine Lawson Human-on-the-Loop: The New AI Control Model That Actually Works Aug 4th 2025 8:00am, by Steve Wilson IT Orchestration Is the Secret Behind Smooth, Scalable IT Operations Aug 3rd 2025 10:00am, by Prashanth Nanjundappa 2 Fixes Vastly Cut TiKV Write Stalls From SST File Ingestion Oct 24th 2025 11:00am, by Jinpeng Zhang Make Data Ready for AI With Hygiene, Governance, and Experimentation Oct 19th 2025 10:00am, by Brian Luisi Platform vs. Analytics Engineer: Why Your Team Needs Both Oct 17th 2025 7:00am, by Ashok Singamaneni and Gaurav Nanda Need a Google Workspace Alternative? Try Sync-in Oct 12th 2025 8:00am, by Jack Wallen The New Economics of Open Source Data Infrastructure Oct 7th 2025 10:00am, by Anil Inamdar How OpenAI's AgentKit Embeds ChatGPT Into Any Website Oct 23rd 2025 12:03pm, by Janakiram MSV The Rise of JavaScript in Machine Learning Oct 23rd 2025 9:03am, by Loraine Lawson Why AI Is Generating 'Lowest Common Denominator' React Code Oct 22nd 2025 12:00pm, by Loraine Lawson React Foundation Leader on What's Next for the Framework Oct 21st 2025 11:05am, by Loraine Lawson Should You Go All-In on Vite? A Risk vs. Reward Analysis Oct 21st 2025 9:00am, by Alexander T. Williams Eliminating the Precision-Latency Trade-Off in Large-Scale RAG Oct 3rd 2025 9:00am, by Bonnie Chase 5 AI Extensions to Help Improve Your VS Code Experience Oct 1st 2025 10:00am, by Jack Wallen Clarifai's AI Engine Cuts Costs Without Performance Hit Sep 26th 2025 12:00pm, by Loraine Lawson GPT-5's Enhanced Reasoning Comes With a Steep Hidden Cost Sep 23rd 2025 8:00am, by Prasenjit A. Sarkar Spec-Driven Development: The Key to Scalable AI Agents Sep 18th 2025 11:00am, by Ankit Jain How TARmageddon Compromises Rust Security: A Developer's Guide Oct 24th 2025 10:00am, by Steven J. Vaughan-Nichols Securing the Vibe: Reducing the Risk of AI-Generated Code Oct 24th 2025 5:24am, by Crystal Morin Why Kubernetes Security Is Critical for GenAI Integrity Oct 23rd 2025 2:00pm, by Utpal Bhatt Beyond Namespaces: Why Kubernetes Needs Real Workload Isolation Oct 21st 2025 8:00am, by Lewis Denham-Parry How To Get Bare-Metal GPU Performance in Confidential VMs Oct 21st 2025 4:00am, by Steven J. Vaughan-Nichols How To Build Resilient IT Operations in 4 Steps Oct 24th 2025 9:00am, by Ariel Russo AI Agents Will Eat Enterprise Software, Just Not in One Bite Oct 23rd 2025 1:03pm, by Peter White How To Deploy a Local AI via Docker Oct 23rd 2025 11:00am, by Jack Wallen Speed Plus Safety: Ending the Dev vs. Platform Engineer Clash Oct 23rd 2025 10:00am, by Jeroen van Erp AI Agents in IT: From Hype To Hands-on Impact Oct 22nd 2025 10:00am, by Bill Lobig Wasm 3.0: No Component Model and No 'Docker Moment' Oct 6th 2025 3:00pm, by B. Cameron Gain How Dapr and WebAssembly Team Up for Microservices Oct 2nd 2025 6:00am, by B. Cameron Gain Wasm 3.0 Offers New Way to Handle JavaScript Strings Sep 20th 2025 7:14am, by Loraine Lawson Flutter 3.5 Offers New Developer Experience Features Aug 30th 2025 6:00am, by Loraine Lawson What Debugging JavaScript on WebAssembly Looks Like Aug 20th 2025 3:00pm, by B. Cameron Gain AI Operations CI/CD Cloud Services DevOps Kubernetes Observability Operations Platform Engineering Make Data Ready for AI With Hygiene, Governance, and Experimentation Oct 19th 2025 10:00am, by Brian Luisi How Atlassian Is Driving the AI Agent-Assisted Workflow Oct 17th 2025 11:00am, by Jennifer Riggins The Infrastructure That Powers AI Could Also Break It Oct 15th 2025 6:00am, by Nir Ohfeld How To Measure AI's Organizational Impact Oct 10th 2025 12:00pm, by Steve Fenton How You.com Survived ChatGPT With a Pivot to Enterprise AI Oct 3rd 2025 7:00am, by Richard MacManus When To Use Synthetic Monitoring vs. Real User Monitoring Oct 24th 2025 6:00am, by Virna Sekuj Rust vs. C++: a Modern Take on Performance and Safety Oct 22nd 2025 2:00pm, by Zziwa Raymond Ian Paved Roads, Golden Paths, Guardrails and Railroads Oct 22nd 2025 11:00am, by Dario Esposito Technical Debt vs. Architecture Debt: Don't Confuse Them Oct 22nd 2025 6:00am, by Nadzeya Stalbouskaya How Thrivability ROI Tackles the Cognitive Load Crisis Oct 21st 2025 10:00am, by Betty Junod Why Google Cloud's OTLP Support Matters for Your Telemetry Pipeline Oct 20th 2025 3:00pm, by B. Cameron Gain OpenStack Flamingo Reduces Technical Debt, Boosts Performance Oct 7th 2025 11:00am, by Steven J. Vaughan-Nichols Why FinOps Isn't About Saving Money Oct 3rd 2025 10:00am, by Vicki Walker Real-World IT Sustainability: 3 Case Studies From Green IO London Oct 2nd 2025 10:00am, by Charles Humble How Distributed Postgres Solves Cloud's High-Availability Problem Sep 11th 2025 9:00am, by Meredith Shubel Beyond Basic Scaling: Advanced Kubernetes Resource Strategies Oct 24th 2025 7:30am, by Vicki Walker Paved Roads, Golden Paths, Guardrails and Railroads Oct 22nd 2025 11:00am, by Dario Esposito When JSDOM and Fetch Collide: Cross-Environment Lessons Oct 18th 2025 10:00am, by Gabor Koos Developers Want to Build, Not Battle Friction Oct 16th 2025 8:00am, by Dustin Kirkland Ulysses' Odyssey: Lessons for Platform Engineering Oct 16th 2025 6:00am, by William Rizzo Beyond Basic Scaling: Advanced Kubernetes Resource Strategies Oct 24th 2025 7:30am, by Vicki Walker Why Kubernetes Security Is Critical for GenAI Integrity Oct 23rd 2025 2:00pm, by Utpal Bhatt The Challenges of Uniting VMs and Containers on a Single Platform Oct 22nd 2025 7:00am, by Dean Lewis Beyond Namespaces: Why Kubernetes Needs Real Workload Isolation Oct 21st 2025 8:00am, by Lewis Denham-Parry Why Modern IPv6 Failed This Massive Kubernetes Networking Test Oct 20th 2025 12:00pm, by Steven J. Vaughan-Nichols When To Use Synthetic Monitoring vs. Real User Monitoring Oct 24th 2025 6:00am, by Virna Sekuj Unblock DevEx by Getting Observability Tools Out of Their Way Oct 23rd 2025 3:00pm, by Vicki Walker Why Google Cloud's OTLP Support Matters for Your Telemetry Pipeline Oct 20th 2025 3:00pm, by B. Cameron Gain Why Synthetic Tracing Delivers Better Data, Not Just More Data Oct 17th 2025 12:00pm, by Gerardo Dada Observability Is Stuck in the Past. Your Users Aren't Oct 17th 2025 6:00am, by Andrew Tunall How To Build Resilient IT Operations in 4 Steps Oct 24th 2025 9:00am, by Ariel Russo Multipass: Fast, Scriptable Ubuntu VMs for Modern DevOps Oct 24th 2025 7:00am, by Janakiram MSV When To Use Synthetic Monitoring vs. Real User Monitoring Oct 24th 2025 6:00am, by Virna Sekuj Speed Plus Safety: Ending the Dev vs. Platform Engineer Clash Oct 23rd 2025 10:00am, by Jeroen van Erp Breaking the 'Shared-Nothing' Bottleneck: A NoSQL Paradigm Oct 23rd 2025 8:00am, by Carol Platz Beyond Basic Scaling: Advanced Kubernetes Resource Strategies Oct 24th 2025 7:30am, by Vicki Walker Speed Plus Safety: Ending the Dev vs. Platform Engineer Clash Oct 23rd 2025 10:00am, by Jeroen van Erp Why Up to 70% of Platform Engineering Teams Fail to Deliver Impact Oct 22nd 2025 1:05pm, by Jennifer Riggins Paved Roads, Golden Paths, Guardrails and Railroads Oct 22nd 2025 11:00am, by Dario Esposito Ulysses' Odyssey: Lessons for Platform Engineering Oct 16th 2025 6:00am, by William Rizzo C++ Developer tools Go Java JavaScript Programming Languages Python Rust TypeScript Rust vs. C++: a Modern Take on Performance and Safety Oct 22nd 2025 2:00pm, by Zziwa Raymond Ian Building a Real-Time System Monitor in Rust Terminal Oct 15th 2025 7:05am, by Tinega Onchari SQL vs. Python: Frenemies of the Data World Oct 14th 2025 7:00am, by Ivan Novick The 'Obfuscated C Code Contest' Confronts the Age of AI Aug 17th 2025 6:00am, by David Cassel How AI Can Help You Learn the Art of Programming Jun 20th 2025 9:00am, by Jack Wallen Unblock DevEx by Getting Observability Tools Out of Their Way Oct 23rd 2025 3:00pm, by Vicki Walker As Vibe Coding Fades, Woz Offers Production-Ready Alternative Oct 21st 2025 3:00pm, by Darryl K. Taft Can Arduino Teach a Tech Giant How To Win Over Developers? Oct 14th 2025 6:15am, by Mary Branscombe A Hands-On Review of Conductor, an AI Parallel Runner App Oct 11th 2025 7:00am, by David Eastman New React Foundation To Manage Framework Oct 11th 2025 6:00am, by Loraine Lawson Go Experts: 'I Don't Want to Maintain AI-Generated Code' Sep 28th 2025 6:00am, by David Cassel How To Run Kubernetes Commands in Go: Steps and Best Practices Jun 27th 2025 8:00am, by Sunny Yadav Prepare Your Mac for Go Development Apr 12th 2025 7:00am, by Damon M. Garn Pagoda: A Web Development Starter Kit for Go Programmers Mar 19th 2025 6:10am, by Loraine Lawson Microsoft TypeScript Devs Explain Why They Chose Go Over Rust, C# Mar 18th 2025 7:00am, by David Cassel Why Bloomberg Chose Vendor-Neutral Java Over Big Tech Oct 2nd 2025 5:00pm, by Darryl K. Taft Microsoft AI Agents Automate Enterprise Java and .NET Migrations Sep 26th 2025 4:00pm, by Darryl K. Taft Java 25: Oracle Makes Java Easier To Learn, Ready for AI Development Sep 18th 2025 4:00pm, by Darryl K. Taft Vibe Coding Fails Enterprise Reality Check Sep 10th 2025 4:00pm, by Darryl K. Taft New Tool Ends Java Configuration Nightmare in K8s Aug 21st 2025 3:00pm, by Darryl K. Taft The Rise of JavaScript in Machine Learning Oct 23rd 2025 9:03am, by Loraine Lawson Why AI Is Generating 'Lowest Common Denominator' React Code Oct 22nd 2025 12:00pm, by Loraine Lawson React Foundation Leader on What's Next for the Framework Oct 21st 2025 11:05am, by Loraine Lawson Should You Go All-In on Vite? A Risk vs. Reward Analysis Oct 21st 2025 9:00am, by Alexander T. Williams When JSDOM and Fetch Collide: Cross-Environment Lessons Oct 18th 2025 10:00am, by Gabor Koos Rust vs. C++: a Modern Take on Performance and Safety Oct 22nd 2025 2:00pm, by Zziwa Raymond Ian React Foundation Leader on What's Next for the Framework Oct 21st 2025 11:05am, by Loraine Lawson SQL vs. Python: Frenemies of the Data World Oct 14th 2025 7:00am, by Ivan Novick New React Foundation To Manage Framework Oct 11th 2025 6:00am, by Loraine Lawson New Netlify Agents Offer AI Workflows for Developers Oct 4th 2025 5:05am, by Loraine Lawson The Rise of JavaScript in Machine Learning Oct 23rd 2025 9:03am, by Loraine Lawson SQL vs. Python: Frenemies of the Data World Oct 14th 2025 7:00am, by Ivan Novick A Cloud Built for Python Data Scientists, Not Infrastructure Engineers Oct 5th 2025 6:00am, by David Cassel Why Python Data Engineers Should Know Kafka and Flink Oct 1st 2025 8:00am, by Diptiman Raichaudhuri Python Dataclasses: A Complete Guide to Boilerplate-Free Objects Sep 26th 2025 3:00pm, by Jessica Wachtel How TARmageddon Compromises Rust Security: A Developer's Guide Oct 24th 2025 10:00am, by Steven J. Vaughan-Nichols Rust vs. C++: a Modern Take on Performance and Safety Oct 22nd 2025 2:00pm, by Zziwa Raymond Ian Building a Real-Time System Monitor in Rust Terminal Oct 15th 2025 7:05am, by Tinega Onchari How Vite Became the Backbone of Modern Frontend Frameworks Sep 26th 2025 9:00am, by Richard MacManus Microsoft Goes All-in on Rust for Core Infrastructure and Much More Sep 19th 2025 5:00pm, by Darryl K. Taft Microsoft TypeScript Devs Explain Why They Chose Go Over Rust, C# Mar 18th 2025 7:00am, by David Cassel Go Power: Microsoft's Bold Bet on Faster TypeScript Tools Mar 12th 2025 1:00pm, by Darryl K. Taft and Loraine Lawson Oracle Won't Release 'JavaScript' Without a Fight Jan 11th 2025 5:00am, by Loraine Lawson The Year in JavaScript: Top JS News Stories of 2024 Dec 27th 2024 6:30am, by Loraine Lawson How OOP Developers Can Get To Know TypeScript Through Deno Oct 19th 2024 8:00am, by David Eastman 2025-10-22 06:00:33 Technical Debt vs. Architecture Debt: Don't Confuse Them contributed, AI / CI/CD / Operations Technical Debt vs. Architecture Debt: Don't Confuse Them Architecture debt silently sabotages AI, cloud and transformation initiatives. Learn the difference, how to diagnose those systemic issues and fix them. Oct 22nd, 2025 6:00am by Nadzeya Stalbouskaya Featued image for: Technical Debt vs. Architecture Debt: Don't Confuse Them Featured image by Vicente Sargues on Shutterstock. Developers, project managers and even executives use the term "technical debt" to explain delays, instability or rising maintenance costs. Its meaning is simple and relatable: We cut corners to deliver faster, take on "debt" and later repay it through bug fixes, refactoring or rewriting code. Yet, there is another, far more dangerous type of debt: architecture debt. Unlike technical debt, architecture debt is not visible in a pull request. It doesn't appear as a broken unit test or a security vulnerability in a code scanner. It grows silently when the overall structure of systems, integrations and processes is flawed. It's systemic rather than local, and it often reveals itself only when a transformation program stalls, a cloud migration fails or an AI initiative cannot scale. So why do companies so often confuse technical debt with architecture debt? And why does this confusion cost businesses millions? The House vs. City Metaphor Imagine a house. If a stair breaks, a pipe leaks or the electrical wiring fails, everyone notices right away. These are visible problems that demand immediate repair. In IT terms, this is technical debt: a local issue in the codebase, test coverage or infrastructure. One team, or even one engineer, can usually address it. It may be painful, but it is tangible, diagnosable and often well understood. Visual damage to house vs. invisible problems with house. Now imagine an entire city. Every house might be freshly painted, every apartment renovated, every room in perfect condition. Yet, if the city's road network is poorly designed, if the water supply is fragmented or if zoning rules are inconsistent, the city will gradually descend into dysfunction. Traffic jams will paralyze movement, residents will waste hours commuting and emergency services won't reach their destinations in time. This is architecture debt. It doesn't manifest as a single broken stair -- it reveals itself in systemic failures caused by misalignment and lack of coordination across the whole environment. Dysfunctional city vs. functional city. The same principle applies to IT landscapes. A development team might deliver clean, modular code. CI/CD pipelines may run flawlessly, and tests all pass in green. Yet beneath this surface, the enterprise often runs multiple overlapping platforms with fragile, undocumented point-to-point integrations. Architectural principles exist on paper but are inconsistently enforced. The result is predictable: Every new initiative, from digital transformation to AI adoption, encounters hidden friction and costly delays. The metaphor matters because it highlights visibility versus invisibility. Technical debt is obvious -- like a leaky roof you can't ignore. Architecture debt is subtle -- like poor city planning that only becomes undeniable when gridlock makes life unworkable. And while fixing a broken stair is straightforward, redesigning an entire transportation system takes years, coordination and investment. Why Companies Confuse Technical and Architecture Debt * The symptoms look deceptively similar. Both types of debt produce the same visible symptoms: delays, outages and higher costs. But the causes differ: Technical debt stems from code shortcuts, while architecture debt arises from systemic flaws such as platform duplication or broken data governance. Because the outcomes look alike, organizations often mislabel everything as "tech debt," missing the deeper structural cause. * The focus stays on fixing code. Executives often fall back on a default response: "If we just hire more developers, we'll clear the backlog." This works when the problem is technical debt -- adding engineers can indeed accelerate refactoring or bug fixes. But architecture debt doesn't yield to brute force. Ten extra developers cannot fix platform sprawl, reconcile fragmented data models or redesign an integration landscape. These are structural issues that require governance, architecture boards and cross-domain design, not simply more coding power. * Architecture debt hides in plain sight. Technical debt has clear indicators: bug density, test coverage, code complexity scores. These appear naturally in developer dashboards and project reports. Architecture debt, however, rarely shows up in Jira tickets or automated scans. Few organizations track duplicate platforms, undocumented interfaces or integration complexity. Without such metrics, architecture debt remains invisible until a major transformation grinds to a halt. * Organizational silos reinforce the confusion. Most teams optimize for their own scope. A development squad ensures its microservice runs smoothly. A project manager hits local milestones. A vendor delivers a contract. But no one owns the end-to-end structure -- the city rather than the house. Architecture decisions become scattered: One domain picks a new Software as a Service tool, another adopts its own data model, a third chooses a different cloud provider. Over time, these siloed decisions accumulate into architecture debt that no single team recognizes until it is too late. * Language itself blurs the lines. "Tech debt" has become a catch-all phrase in corporate vocabulary. Business stakeholders rarely distinguish between fixing a brittle function and untangling a decade of integration spaghetti. The term's popularity masks important differences: One is tactical and correctable, the other is strategic and deeply structural. By calling everything "technical debt," companies miss the chance to create practices, funding models and remediation plans specifically designed for architecture debt. Diagnosing Architecture Debt For specialists, the key is to make the invisible visible. Techniques include the following. * Duplicate platforms: Count how many systems perform overlapping functions (five human resources systems, three customer-relationship management tools). High duplication signals structural inefficiency. * Integration complexity: Measure the number of point-to-point connections versus API gateways, enterprise service buses (ESBs) or event-driven models. * Principle violations: Track how many systems lack defined owners, documented interfaces or compliance with enterprise standards. * Latency chains: Calculate end-to-end data flow time across multiple hops. If data must pass through six legacy systems before reaching an AI model, architecture debt is the bottleneck. * Configuration management database (CMDB) completeness: Use ServiceNow or a similar tool to measure the percentage of applications with filled ownership, life cycle and dependency fields. These metrics help shift architecture debt from abstract concept to quantifiable problem. Real-World Cases AI adoption blocked by data silos A company builds advanced machine learning (ML) models to forecast demand. The data scientists are skilled, the models promising. But data resides in five separate legacy systems with no unified schema. Integration projects drag on for months. The result: The AI program stalls, not because of poor algorithms, but because of architecture debt in data pipelines. Cloud migration and the immovable legacy During a cloud migration, 30% of applications can't move. They depend on outdated middleware, proprietary protocols or undocumented dependencies. The migration slows, and costs skyrocket. The issue is architecture debt in integration and platform dependencies, not technical debt in the code. Resilience gaps in infrastructure An enterprise invests heavily in monitoring and incident response. Still, outages persist. The real culprit: an outdated network architecture designed for 2005 traffic patterns, not modern workloads. This is architecture debt in infrastructure design, invisible to dashboards focused only on uptime. The Consequences of Ignoring Architecture Debt * Financial waste: Garner and McKinsey studies show that up to 40% of digital transformation budgets are consumed by untangling hidden architectural problems. Because these costs rarely appear in business cases, programs that start with a $50 million budget can balloon to $70 million to $80 million once hidden dependencies surface. * Program delays: Architectural weaknesses extend timelines dramatically. A 12-month program often drifts into 24 to 36 months once hidden silos or outdated middleware emerge, and many deliver only a fraction of their intended value because resources are consumed by firefighting. For specialists, unresolved architecture debt is the single biggest threat to predictable delivery -- more damaging than resourcing gaps or shifting requirements. * Technological stagnation: Architecture debt locks companies into the past. AI, automation and cloud adoption initiatives don't fail because teams lack skill. They fail because underlying systems are fragmented, unscalable or incompatible. In fact, 70% to 80% of AI projects fail to scale beyond pilot. Without a unified data platform, AI models never leave the lab. Without rationalized applications, automation pilots don't scale. Without decoupled integration, cloud migrations stall. The result: Organizations spend years talking about innovation while still running critical processes on legacy mainframes or fragile middleware. * Increased risk exposure: Old integrations and outdated platforms are not just inefficient -- they are dangerous. Legacy systems were a contributing factor in over 60% of major cyber incidents. Architecture debt creates hidden single points of failure, undocumented dependencies and weak security perimeters. A minor outage in one system can cascade into a businesswide incident. Similarly, fragmented landscapes increase the attack surface for cyber threats, while lack of resilience planning undermines business continuity. For highly regulated industries, this also translates into compliance risk: Auditors increasingly expect evidence that architectural controls are in place, not just operational ones. * Erosion of trust (new, expanded consequence): Perhaps the most subtle consequence is the erosion of trust between IT and the business. When every initiative runs over budget, misses deadlines or delivers less than promised, stakeholders lose faith in IT's ability to execute. This reputational damage is difficult to repair and often leads to shadow IT -- business units bypassing enterprise processes altogether. Ironically, this only accelerates the accumulation of new architecture debt. [d1822104-image2] What Can Be Done: 5 Steps 1. Officially define architecture debt. Organizations must recognize architecture debt as a category distinct from technical debt. This requires clear definitions and communication to both technical and business leaders. 2. Build metrics and dashboards. Track the following: * The percentage of systems without owners. * Point-to-point integrations. * CMDB completeness and accuracy. * The percentage of platforms aligned with architectural principles. 3. Practice architecture observability. Just as site reliability engineers monitor service reliability, architects must monitor the structural health of the IT landscape: scalability, modularity, principle adherence. 4. Run architecture reviews. Beyond code reviews, organizations should hold systematic architecture reviews for projects and domains. 5. Manage debt as a portfolio. Not all debt needs immediate repayment. Like managing a financial portfolio, organizations should prioritize by business impact -- addressing the costliest blockers first while consciously tolerating manageable inefficiencies. Expanded Specialist Insights * Integration patterns matter. The choice of integration architecture is often the difference between manageable complexity and long-term paralysis. Point-to-point integrations may work in the short term, but they scale poorly. Every new system exponentially increases dependencies. By contrast, API-first strategies and event-driven architectures decouple services, reduce systemic coupling and improve resilience. For specialists, this isn't just a design preference, it's a debt-management strategy. Shifting from legacy ESB spaghetti to asynchronous event hubs or API gateways can lower failure domains, speed up onboarding of new services and cut integration costs by double digits. * Governance is architecture in action. Architecture isn't just diagrams; it's the operational discipline of enforcing standards. Without governance boards, review gates and principal compliance checks, architecture debt grows faster than it can be repaid. Effective governance creates a feedback loop: Each project is reviewed not just for delivery but for alignment with long-term enterprise principles. Specialists know that without governance, every "local optimization" becomes tomorrow's systemic problem. For example, allowing teams to adopt overlapping SaaS tools without architectural oversight results in fragmented landscapes that later block consolidation and automation. * Link debt to business KPIs. Architecture debt becomes meaningful to executives only when it connects to business outcomes. Instead of abstract warnings, architects should show how debt directly slows time to market, increases operating cost per transaction or reduces system resilience during incidents. For example, duplicating finance platforms may not look critical until leaders see the effect: increased reconciliation time, higher audit risks and slower financial close -- a challenge reported by 42% of CFOs in Deloitte's 2023 Finance Transformation Survey. By translating architectural debt into the same KPIs tracked at the board level, specialists ensure visibility and funding for remediation. [8e92b741-image3] * Architecture debt and AI. The rise of AI amplifies the risks of architecture debt. AI models thrive on clean, accessible and governed data, yet architecture debt often means data silos, inconsistent schemas and poor lineage tracking. Even world-class models will fail to scale if pipelines are fragmented or unobservable. For specialists, this means architecture is no longer just an IT foundation, it is a direct enabler of AI success. A single broken data lineage can undermine model explainability, making regulatory compliance impossible. Conversely, organizations that actively reduce architecture debt in their data ecosystems gain a competitive edge: Their AI initiatives reach production faster and deliver measurable business outcomes. * Think of observability beyond code. Most observability practices today focus on applications and infrastructure -- uptime, latency, error rates. But architecture debt requires a new dimension of observability: structural monitoring. This means tracking system dependencies, integration bottlenecks and principal compliance in near-real time. For example, dashboards that show the percentage of undocumented APIs or latency across data pipelines allow architects to detect architecture debt before it cripples delivery. Just as site reliability engineers measure reliability, architects must measure structural health. * Adopt portfolio thinking for debt remediation. Not all debt can or should be repaid immediately. Treating debt as a portfolio creates discipline: Some items are high-interest and must be resolved quickly (such as undocumented critical integrations), while others can be tolerated if managed (two overlapping SaaS tools in low-risk domains). Using risk-adjusted prioritization allows architects to align remediation with business value, rather than chasing every inefficiency. This approach also helps secure executive funding by linking remediation plans to measurable return on investment. Conclusion Technical debt is visible. Everyone can point to buggy code, missing tests or a legacy function that needs rewriting. Architecture debt is hidden, and that makes it far more dangerous. It accumulates quietly in duplicated platforms, fragile integrations and outdated governance models. And while technical debt slows delivery, architecture debt stalls entire transformations. Looking ahead, organizations that fail to address architecture debt will struggle to adopt AI at scale, modernize for cloud or meet rising cybersecurity and compliance demands. The winners will be those that treat architecture debt as a board-level risk and invest in continuous architecture observability, governance and remediation. For specialists, the message is clear: Stop treating "tech debt" as a catch-all phrase. Build the practices, metrics and governance to make architecture debt visible and actionable. In the era of AI and data-driven enterprises, reducing architecture debt will no longer be a technical choice. It will be a strategic differentiator that separates the companies that can transform from those that will fall behind. TRENDING STORIES YOUTUBE.COM/THENEWSTACK Tech moves fast, don't miss an episode. Subscribe to our YouTube channel to stream all our podcasts, interviews, demos, and more. SUBSCRIBE Created with Sketch. [55f567cf-c] Nadzeya Stalbouskaya is a technology architect, prolific author and international conference speaker. In numerous global publications, she is an emerging voice shaping the future of enterprise architecture and digital transformation. Nadzeya is an active member of leading industry organizations, serving... Read more from Nadzeya Stalbouskaya SHARE THIS STORY TRENDING STORIES TNS owner Insight Partners is an investor in: Real. SHARE THIS STORY TRENDING STORIES TNS DAILY NEWSLETTER Receive a free roundup of the most recent TNS articles in your inbox each day. [ ] SUBSCRIBE The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our Terms of Use and Privacy Policy. ARCHITECTURE Cloud Native Ecosystem Containers Databases Edge Computing Infrastructure as Code Linux Microservices Open Source Networking Storage ENGINEERING AI AI Engineering API Management Backend development Data Frontend Development Large Language Models Security Software Development WebAssembly OPERATIONS AI Operations CI/CD Cloud Services DevOps Kubernetes Observability Operations Platform Engineering CHANNELS Podcasts Ebooks Events Webinars Newsletter TNS RSS Feeds THE NEW STACK About / Contact Sponsors Advertise With Us Contributions roadmap.sh Community created roadmaps, articles, resources and journeys for developers to help you choose your path and grow in your career. Frontend Developer Roadmap Backend Developer Roadmap Devops Roadmap (c) The New Stack 2025 Disclosures Terms of Use Advertising Terms & Conditions Privacy Policy Cookie Policy FOLLOW TNS * *