Clouds
Five clouds, one way of working: landing zones as code, a decision per workload, waves, then operations — on each provider's own framework and tools.
Explore Clouds
5 topics, each with an overview and a few short pages.
Frequently asked questions
What customers ask first.
No. NGT delivers on AWS, Microsoft Azure and Google Cloud, and on Huawei Cloud and Alibaba Cloud. The method is the same; the tools are each cloud's own.
Both. A new platform starts from the same landing zone, with containers, managed data stores, pipelines and monitoring in place before the first release.
With an assessment of the estate, or with a landing zone for a first workload. Both follow Microsoft's Cloud Adoption Framework, and a pilot proves the pattern before migration waves start.
Microsoft's own: Azure Migrate to discover, assess and move servers; Database Migration Service, Data Migration Assistant and SQL Server Migration Assistant for databases; Azure Monitor and Log Analytics once systems are live.
With an assessment of the estate, usage and billing data, then a plan and a pilot of one low-risk workload. The launch follows only once the pilot has checked performance, stability and cost.
Google's own: Migrate to Virtual Machines for servers, Database Migration Service for databases, and Cloud Monitoring and Cloud Logging from the first day. The foundation is written in Terraform.
Usually lower infrastructure cost, or a second public cloud so as not to depend on one provider. NGT keeps the same pipelines and the same way of working on every cloud, so a second cloud does not mean a second way of delivering.
Huawei Cloud's own: Server Migration Service for servers, Data Replication Service for databases and Object Storage Migration Service for files and objects. The landing zone is written in Terraform.
