1. Cloud architecture in line with (development) policy
Seeing as established parameters apply, developers (for example) work within a well-defined playing field. This means companies do not run the risk of applications being developed within their cloud environment that are at variance with the organisation’s compliance policy, for example. Likewise the IT manager has fewer concerns about compliance because this is embedded in the foundation of the IT infrastructure.
2. Speed and scalability
As already described above, a migration to the cloud can take place much more quickly thanks to a landing zone. The preparation time is drastically reduced: whereas it used to take at least a day, with a landing zone the time is cut to a few minutes. As you can well imagine, this yields considerable cost savings. A landing zone also leads to a shorter time-to-market for new applications, resulting in DevOps processes being set up more quickly and efficiently. Scalability is another major feature inherent in a landing zone, since it is easy to carry out an extension to new environments. This means that standard profiles, for example, can easily be applied to new users.
3. Security and compliance
Thanks to the guardrails, compliance constitutes an integral part of a landing zone, meaning developers and engineers can work within the landing-zone environment safely and in observance of the compliance rules. What is more, organisations do not spend so much time on implementing complex rules within their public cloud, and the risk of shadow IT is thereby substantially reduced. This applies particularly to the operational phase. But it doesn’t stop with the one-off setting-up of the environment(s); it’s also about keeping all environments up to date in an ongoing and uniform manner.
A landing zone has a high degree of standardisation, meaning engineers work simply with environments that have been developed by others. Moreover, a good landing zone is API driven, so that the implementation of new applications is rendered simple, should this be necessary. This flexibility saves time when the landing-zone environment is scaled up or extended.
5. Better grasp of the costs
It’s a well-known pitfall: organisations quickly lose control of their cloud expenses because they do not have a clear overview of the solutions being used – and the costs attached to them. In a landing zone frameworks are established within which engineers are free to develop new initiatives, without this leading to unexpected and unnecessary costs. Furthermore, the process can be set up in such a way that every account/subscription is visible. This avoids situations in which accounts (and therefore costs) remain under the radar.
Who is it suitable for?
So there are advantages aplenty. But which developers does a landing zone offer most possibilities to, and which organisations take best advantage of it? Two aspects play a major role when it comes to answering this question.
Cloud Engineer at Sentia and specialised, among other things, in landing zones. At Sentia he is involved in the development of the Sentia Halloumi Landing Zone solution.