Beyond the Hype: Unveiling the Multi-Cloud Mirage in Public Sector Cloud Strategy

Introduction

The APS's shift to cloud computing has been underway for some time, with many Departments adopting a 'cloud-first' mentality that often included a multi-cloud strategy. While the intent was to foster resilience and take advantage of competitive offerings, it's time to reflect on what these choices mean for the APS today. For those Departments that have not yet fully transitioned, and for those that find themselves amidst the complexities of multi-cloud management, a critical evaluation is necessary.

This article seeks to provide insights into why a single-cloud strategy may be more advantageous and how it can mitigate the risks that are currently obscuring the full potential of the cloud for Public Service organisations.

Note: This is not a comprehensive article of all my thinking, as most wont read it. But this sets the scene for further discussion.

Revisiting the Multi-Cloud Strategy

The multi-cloud approach was initially appealing for several reasons:

• Resilience: The strategy aimed to distribute business system components and/or systems across various providers to enhance disaster recovery and system reliability.
• Choice and Flexibility: The variety of services offered through WWhole of Government (WofG) agreements was seen as an opportunity to select 'best-of-breed' solutions and avoid vendor lock in.

However, the practical experience has highlighted several challenges:

• Resilience Compromised: The complexities of multi-cloud management can create more operational challenges than they solve.
• Choice Overload: The breadth of services available can lead to decision paralysis or the selection of solutions that do not align with actual usage needs, introducing unnecessary risk. While also increasing cost due to poor cloud architectures, multiple networking backbones, and overall duplication.

Therefore, as the APS matures in its cloud adoption, the lessons learned point to the need for a more streamlined and focused approach.

The Complexity Conundrum

The reality is, the pursuit of a multi-cloud strategy has led to unforeseen consequences:

• Skillset Dispersion: The APS's limited pool of cloud engineering talent is spread across multiple platforms, which can and has diluted expertise.
• Operational Overload: The challenge of mastering multiple cloud services can detract from the core tasks of developing staff capabilities, refining governance, and creating optimal cloud solutions.

This complexity has lead to suboptimal use of resources and hinders the APS's ability to deliver on the benefits cloud computing offers. It has also complicated architectual and governance processes which has lead to poorly architected solutions and limited focus on critical drivers i.e. cost.

Rethinking Early Cloud Decisions

The initial fear of vendor lock-in that drove many to take up a multi-cloud strategy also needs reevaluation in light of current experiences:

• Service Optimisation: Building a strong relationship with a single vendor can lead to better-tailored services for the APS's needs. As utilisation of a single vendor's multiple regions/zones, is more resilient than the dual data centre approach taken by Departments today.
• Skill Concentration: Focusing on one platform allows for deeper staff development and a more robust cloud capability.
• Governance Streamlining: A single-cloud strategy simplifies governance, enabling more effective decision-making, cloud application management and cloud financial management - as the FOCUS specification from the FinOps Foundation has only just entered the scene to streamline normalisation efforts of complex billing & usage data.

Mastering the Cloud

For the APS, it is my opinion that mastering a single cloud environment is a prerequisite before considering a multi-cloud approach. Mastery involves leveraging the cloud's capabilities to achieve operational excellence and adapt to the new responsibilities that cloud computing brings - which is a far cry from how Departments operate today.

The Benefits of a Unified Approach

• FinOps Efficiency: Centralising cloud services with one provider simplifies financial operations and enables more effective cost management. Especially as it relates to architecting for success. See my article here on this matter positioned in the concept of a Continuous Authority to Operate (cATO) by bringing FinOps early in the architectual governance processes:
• Operational Simplicity: A single cloud environment reduces governance and operational complexities, leading to stronger compliance, security, and management.
• Depth of Expertise: Focusing on one cloud platform allows teams to develop deep expertise, driving innovation and operational efficiency. Importantly, when it comes to learning whats fit for purpose in the cloud - as many workloads aren't, unless they are refactored/replatformed.

Strategic Considerations for Expansion

The APS should only consider expanding its cloud strategy after achieving a high level of proficiency with a single cloud environment. Expansion should be based on strategic needs, not on a default desire for diversity or the allure of advanced services.

Conclusion

The APS's journey to the cloud is an ongoing process that requires careful consideration of past decisions and current strategies. A single-cloud strategy offers a more effective path to realising the cloud's transformative potential. Mastery of one cloud environment is essential to ensuring operational efficiency, robust governance, and the adaptability necessary to meet the evolving demands of public service.

Departments that have already embarked on a multi-cloud strategy should take stock of the challenges they face and consider consolidating their approach. For those still transitioning, the insights gained point towards the benefits of a single-cloud strategy. By adopting a disciplined approach, the APS can ensure that cloud adoption is not only effective but also delivers on its transformative promise for the Australian public.

Thanks for reading.

The views expressed in this article are my own and do not represent that of my employer, or any of my clients.

#multicloud #aps #finops #strategy