Monolithic Landing Zone

⭐️⭐️☁️ PlatformLanding Zones includes a common set of core resources like virtual networks. These resources are managed with the same life-cycle as the underlying cloud tenant.

Early stage cloud foundations often start with a β€œone-size-fits-all” approach to Landing Zones. This means that the baseline configuration provisioned and enforced by the landing zone has to serve multiple concerns. For example the landing zone may include a prescriptive network configuration for enabling On-Premise Network Connection as well as mandatory audit configuration (see Centralized audit logs ). When the Cloud Foundation team encounters a new concern, like Managed DevOps Toolchain , it also gets added to the baseline. Because different DevOps teams have different needs most Cloud Foundations will split up an organically grown Monolithic Landing Zone into Modular Landing Zones. The pain points frequently encountered are listed in the last section of this page.

The Monolithic Landing Zone is known to be a local maximum that keeps complexity low in the short term while sacrificing flexibility in the long term.

When to Build a Monolithic Landing Zone

⚠️ For Cloud Foundation that are getting started with building Landing Zones the Monolithic Approach is considered an anti-pattern. A modular approach as laid out in Modular Landing Zones is recommended.

For Cloud Foundations that find themselves with organically grown Monolithic Landing Zone, the next section will help to decide when to re-structure existing Monolithic Landing Zones.

Pain Points of Monolithic Landing Zone

As Cloud Foundations serve more customers the limitations of the Monolithic Landing Zone approach will become more numerous. Here are indicators that your Cloud Foundation needs to move to Modular Landing Zones:

  • Every time a customer wants to book a service, it is added to the Monolithic Landing Zone.

  • The Monolithic Landing Zone creates workload that is not required by some teams.

  • The Monolithic Landing Zone hosts conflicting combinations like different Managed DevOps Toolchain providers or Virtual Network Services.

  • Customers request different combinations of Landing Zone services that are managed with a growing number of feature-toggles.

  • Re-using parts of Monolithic Landing Zone is not easily possible for other Landing Zones.

  • meshStack

    meshStack enables you to create monolithic landing zones for all major public/private cloud platforms: - AWS - Azure - GCP - OpenShift - Kubernetes

    Learn More open in new window
Last Updated: