> Markdown version of [/videos/1960-why-segmenting-your-infrastructure-into-tiers-makes-your-infrastructure-design-better](https://www.wearedevelopers.com/videos/1960-why-segmenting-your-infrastructure-into-tiers-makes-your-infrastructure-design-better). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Why segmenting your infrastructure into tiers makes your infrastructure design better

Transform unmanageable infrastructure monoliths into scalable systems by segmenting resources into logical tiers. This explicit boundary reduces blast radius, speeds up deployments, and safely empowers application developers.

- **Speakers:** [Thameez Bodhanya](https://www.wearedevelopers.com/@thameez-bodhanya)
- **Event:** World Congress 2026 Europe - Virtual Stage
- **Published:** July 2, 2026
- **Duration:** 27:13
- **URL:** https://www.wearedevelopers.com/videos/1960-why-segmenting-your-infrastructure-into-tiers-makes-your-infrastructure-design-better

## Summary

Ad hoc infrastructure-as-code deployments typically evolve into unmanageable monoliths with dangerous blast radii or fragmented workspaces plagued by fuzzy dependencies. To solve this, organizations can adopt infrastructure tiering: an intentional approach to segmenting resources logically. By dividing infrastructure into distinct levels—each building explicitly on the previous one—teams establish clear boundaries, reduce deployment times, and minimize the risk of catastrophic system changes.

A successful tiering strategy follows a tiered design tailored to a company's specific context and maturity. Tier 0 handles foundational, rarely changed resources like VPCs and DNS zones, requiring the strictest security oversight. Tier 1 delivers the shared platform—such as Kubernetes clusters, IAM roles, and observability tools—maintained by platform or DevOps teams. Finally, Tier 2 empowers application developers to provision their own databases, web services, and object storage directly alongside their application code. This delegation explicitly shifts ownership, allowing development squads to operate at their own pace while assuming responsibility for maintenance and cost operations.

Crucially, interaction between tiers must rely on flat input and output variables to decouple environments. Passing only specific values—like a VPC ID instead of an entire Terraform module—treats underlying tiers as black boxes and prevents complex dependency webs. Tiers must also cascade sequentially, meaning an application tier should read from the platform tier, never bypassing it to access foundational resources directly. This strict contract-driven architecture not only isolates faults but provides the flexibility to mix tooling, enabling platform engineers to manage foundations in Terraform while application developers deploy infrastructure using AWS CDK or Pulumi. Ultimately, the goal is to "bucket with intention" to build a scalable, secure, and developer-friendly architecture.

**Keywords:** infrastructure tiering, infrastructure as code, terraform remote state, aws cdk, infrastructure bucketing, blast radius reduction, platform engineering, site reliability engineering, vpc segmentation, iac dependency management, ssm parameter store, developer self-service infrastructure, cloud infrastructure architecture, kubernetes cluster provisioning, shared platform infrastructure

## Chapters

1. **Challenges of organic infrastructure bucketing and monolith workspaces** (01:51) — Grouping infrastructure without intention leads to deployment bottlenecks and massive blast radiuses.
1. **Defining infrastructure tiering with intentional workspace bucketing** (06:16) — Logical collections of related infrastructure resources are built independently using flat input and output variables.
1. **Breaking down foundational, shared, and application infrastructure tiers** (09:07) — Assigning specific infrastructure layers like data centers, platform resources, and application services into distinct tiers simplifies management.
1. **Real-world workspace implementations across different cloud provider environments** (14:39) — Practical examples of flat outputs and remote state sharing demonstrate successful implementations across multiple cloud providers.
1. **Scaling benefits and organizational impacts of tiered infrastructure design** (22:10) — Designing tiered environments reduces blast radius, speeds up deployment, and clarifies resource ownership.

## Related Moments

- [Executing infrastructure provisioning and teardown via Terraform Cloud](https://www.wearedevelopers.com/videos/1221-infrastructure-as-code-the-developer-s-secret-weapon) (from "Infrastructure as Code: The Developer's Secret Weapon")
- [Overview of infrastructure as code tools](https://www.wearedevelopers.com/videos/740-the-power-of-cloud-development-kit-cdk-how-to-get-the-most-out-of-it) (from "The power of Cloud Development Kit (CDK): How to get the most out of it")
- [Transforming engineering workflows through infrastructure as code](https://www.wearedevelopers.com/videos/930-unleashing-potential-across-teams-the-power-of-infrastructure-as-code) (from "Unleashing Potential Across Teams: The Power of Infrastructure as Code")
- [Best practices for writing and maintaining Terraform code](https://www.wearedevelopers.com/videos/1221-infrastructure-as-code-the-developer-s-secret-weapon) (from "Infrastructure as Code: The Developer's Secret Weapon")
- [Fostering team collaboration through common infrastructure abstractions](https://www.wearedevelopers.com/videos/182-gitops-keeps-focus-on-apps-not-on-infrastructure) (from "GitOps keeps focus on apps, not on infrastructure")
- [Deep dive into infrastructure as code with deployment kits](https://www.wearedevelopers.com/videos/1050-the-road-to-mlops-how-verivox-transitioned-to-aws) (from "The Road to MLOps: How Verivox Transitioned to AWS")

## Related Articles

- [How to Avoid Over-Engineering](https://www.wearedevelopers.com/magazine/546-how-to-avoid-over-engineering)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [What Are The Top Skills Required For Azure Developers?](https://www.wearedevelopers.com/magazine/77-what-are-the-top-skills-required-for-azure-developers)
- [Stephan Gillich - Bringing AI Everywhere](https://www.wearedevelopers.com/magazine/489-stephan-gillich-bringing-ai-everywhere)

## Related Jobs

- [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub**
- [Software Engineer L2 - Cloud Infrastructure](https://www.wearedevelopers.com/jobs/ext/1293339-software-engineer-l2-cloud-infrastructure) at **Twilio**
- [Software Engineer L2 - Cloud Infrastructure](https://www.wearedevelopers.com/jobs/ext/1282024-software-engineer-l2-cloud-infrastructure) at **Twilio**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Software Engineer, Platform Engineering (L2)](https://www.wearedevelopers.com/jobs/ext/1956829-software-engineer-platform-engineering-l2) at **Twilio**
- [Platform Engineer (DevOps)](https://www.wearedevelopers.com/jobs/48264-platform-engineer-devops) at **WDW Consulting GmbH**