2. Should Teams Choose Their Own Tooling?
Autonomy is good, but anarchy isn’t. When every team picks its own continuous integration and continuous delivery pipeline, monitoring stack, and secret management tool, officials end up with an unmanageable patchwork. Standardize the platform layer and give teams freedom at the application layer.
3. Should Agencies Transfer Workloads Despite Costs?
Data transfer between clouds can be expensive, and large data sets create gravitational pull. Once a data lake is on AWS, moving compute to GCP for “the best price” may cost more in egress than saved in compute. Map government data flows before making placement decisions.
READ MORE: Modernize your agency’s IT with cutting-edge cloud technology.
4. Does Hiring More People Help To Manage Clouds?
If the response to multicloud complexity is “hire more people,” agencies set out on a losing trajectory. Invest in automation for provisioning, patching, scaling, incident response and cost optimization. Or, outsource to a great team. People should be designing systems, not manually configuring them.
5. Should I Prepare for Disaster Recovery?
Having workloads on multiple clouds might automatically grant agencies some resilience, but it doesn’t automatically provide disaster recovery. Test failover scenarios regularly. Too many organizations discover their multicloud DR strategy doesn’t work the first time they actually need it.
