I have come to notice that “the Cloud” is a big place and that there are many things to consider before diving in. Since the beginning of the year, I have been studying the Microsoft cloud to understand the gears and wheels that help to make it work. In addition, Ive been trying to understand how AWS does similar things with the ultimate goal being to grow an understanding of just how the cloud works. I realize that the computers and resources powering the cloud are not that much different from things that power an in house datacenter or even the laptop I use everyday, but the ways these things are made available and used overall are presented in a new way. This raises the learning curve a bit and I hope to post about my learning process (and progress) here on my blog – yes it runs in the Azure cloud.

My job is in the clouds
I am lucky to get to work in an industry that is growing and changing all the time and the cloud is certainly a big part of that. Being focused on providing the best infrastructure for application development and on what might be the best place to park workloads for clients is an interesting challenge, but certainly one that will be fun to tackle. Since my definition of cloud is likely different from most… “Any compute resources that I cannot physically access” is in some type of cloud. This could be private, hybrid, or public… the owner of the cloud doesn’t matter, these are still cloud resources.

For work the goal is simple, choose the cloud with the best return on investment which provides an environment for best in class client solutions. Sometimes there will be things that live in a public cloud, and other times they will live in a private cloud. As long as they bring the best for the workloads they support that is a success.

Just getting started
Sure I have had access to the cloud for some time and have tinkered off and on for some time, but haven’t spent loads of time getting to know just what’s around. I have taken quite an interest in Azure Resource Templates, to learn how automating or simplifying the effort needed to stand and use resources in the Microsoft cloud. This week, that will continue and hopefully result in some templates getting created soon. While it does not take too long to build and stand up resources, using a general template to speed this up will result in better efficiency over time. I’m excited to tackle these things and begin building top end resources for those I support and maybe those they support.