Hello Cloud fans,
Today I’d like to talk to you about some commonly perceived cloud myths that I’ve encountered in my travels, helping to solve the challenges of getting to the cloud.
It’s simple to use the cloud to SaaS-i-fy my software platform.
A common misconception is that it’s immediately cheaper and easier to provide a software product or service as a subscribed cloud based service over the Internet. However, what some teams can often under-estimate is the operational dependencies it takes to support an application that was built under the assumption that it was being installed into an environment that had all its security, authentication, storage, backup, and recovery already taken care of.
There is no magic support staff in the cloud for all the operational components your software still requires. While you may gain efficiency in dynamically scaling your environment and better streamlining individual client support costs, the real cloud savings come in better understanding all the options available to you in the AWS services catalog and how best to leverage them to reduce costs as you refactor your software platform. All coding is not evil!
Deploying enterprise apps in the cloud is just about pressing some buttons.
When most customers considering deploying their first application into the cloud, they tend to underestimate the effort that is involved in actually building, ing, and deploying that solution. Typically, in a co-lo type deployment there is a great deal of time taken up in the procurement and logistics with getting environments setup, which can cause support challenges and shortcuts to be taken.
Because cloud environments are more dynamic, resources can be created in a much shorter timeframe, but it requires synchronized activity over a more compressed timeframe from a number of different parties including your IaaS provider, your internal application team, and your 3rd party software ISV. Depending on your 3rd party’s relative experience with the AWS cloud, this can be a rewarding or sometimes frustrating and drawn out process. The good news is that once you figure out how to deploy that app, you can easily repeat the process with automated cloud formation and auto-scaling benefits. Fortunately here at 2nd Watch, we’ve done quite a few application deployments in our cloud life!
Becoming cloud savvy is as easy as opening an Amazon account and getting to work spinning up instances.
One of the most expensive mistakes I see with companies approaching the cloud for the first time is having no plan on how to design and create their first environments on the AWS cloud. I mean, how hard could it be? This is Amazon after all. Well, the truth is Amazon Web Services has continued to innovate over the 10 or so years they’ve been doing this cloud thing, and as a result they now have hundreds of services catering to a vast universe of data-center needs.
Properly recognizing both the good design elements of your current IT environment and how best to take advantage of these AWS services is critical to achieving the phenomenal benefits you can realize in operational efficiency, high-availability, and designing best practice environments. Like many other significant choices in life, you can save yourself a lot of pain by getting the advice of a pro you trust before plunging into an unknown subject. Those that just jump in and start turning (and leaving!) stuff on 24×7 without a game plan can wake up with a nasty surprise when they see their first bill.
Let me know what you think in the comments!
-C. Caleb Carter, Solutions Architect