
With the age of distributed computing and cloud-native systems, increasingly more organizations rely on multi-cloud tactics to obtain higher availability, lower vendor lock-in, and scalable scaling of infrastructure. DevOps processes across diverse cloud infrastructures have insurmountable hurdles to standardize, automate, and orchestrate them. This qualitative study delves into the intersection of Infrastructure as Code (IaC), Continuous Integration/Continuous Deployment (CI/CD), and Kubernetes orchestration in multi-cloud DevOps pipelines. From virtual environments and live production, the study contrasts usage of IaC solutions (Terraform and Pulumi) along with automated CI/CD pipelines (GitHub Actions, Jenkins, GitLab CI) for deployment and provisioning apps on AWS, Azure, and GCP. Study also covers Kubernetes as the shared layer for container orchestration, e.g., cross-cloud deployment patterns, auto-scaling, and rollbacks. Quantitative and qualitative data are obtained using benchmark testing, log analysis, and expert interviews. Deployment latency, provisioning accuracy, failback time, and cost-effectiveness are the important performance metrics. Best practices for delivering consistent, resilient, and repeatable infrastructure and applications in multi-cloud deployments are the conclusions of this study. The study concludes with IT leaders, platform architects, and DevOps engineers provided with hands-on advice on implementing cloud-agnostic workflows and achieving reliability, scalability, and automation in multiclouds. It also identifies future DevOps innovation areas in security, policy-as-code, and AI-based orchestration.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
