If you have a Google account, watch Netflix, and stream music from Spotify then congratulations! You can add MultiCloud into your resume buzzword list.
The thing is, we use multiple cloud services without even thinking about it. Using Spotify as the example: the streaming service itself uses another cloud service for authentication (either Facebook or Apple) along with their own native accounts.
By off-loading authentication services to another provider, Spotify can focus on it's core business (streaming music) and their revenue (selling music subscriptions and advertisements). Spotify also streamlines the experience by having users authenticate with other services they frequently use.
In a corporate environment, we are multi-cloud too. Active Directory services offer hybrid support models for on-premises and Azure hosting. If you use Ping Identity for SSO, and CloudFlare as a Content Delivery Network (CDN) on top of your Content Management System(CMS)....Oh BUZZWORD BINGO! It's multi-cloud!
So, the moral of the story is, we were all Multi-Cloud a along. We were just using cloud for services that best meet our needs.
How does that work for businesses? Well that depends. Consider your workload and were it best makes sense to run that workload from a cost and capabilities perspective.
Capabilities
Look at your teams and where their expertise lies. If you have a team of .Net developers and SQL Server DBAs, then where should you host your app? Azure and AWS are the obvious answers. If you have Oracle database and java developers, then maybe you try Oracle Cloud, AWS. If you need to pass data between the two? Well, then you can pick the right option for each and VPN between the two or do both within the same Cloud Service Provider (CSP).
Costs
Understanding costs should be more than a paragraph in a blog post. It should be a novelization into an interesting story (like The Phoenix Project), or someone's full time job. But, the better you understand your workload, the better you'd understand the cost. It would be perilous to consider costs of moving to the cloud in the same way as on-premise data centers; there are too many cost factors.
What factors are those? Data ingress, data egress, data storage, vCPU utilization, backup storage, backup recovery...just to name a few. List price says they are all charged usually nickels or dimes by the hour/gigabyte. The better you understand the workload, the better you know the costs.
Comments
Post a Comment