I have nothing but the utmost respect for DevOps (development operations) people. They are unsung heroes in my opinion. Living in that precarious place between the developers, IT operations, and the business people, their job is to streamline and stabilize operations related to rollout of new applications and code updates to support the business.
When everything is working well, most people forget they are there. Much like offensive linemen in football, the only time people seem to notice them is on those rare occasions when something goes wrong. It doesn’t seem fair, but such is the life of DevOps.
To achieve near continuous deployment for applications, a high degree of automation is essential from the time new code changes hit the source code repository until they are pushed through test, QA, staging and into production. To accomplish that, DevOps teams require a working knowledge of their applications at a system level, as well as a deep understanding of the IT infrastructure (servers, storage, databases and network), to properly marry the two.
Inherent in this process is constant optimization to streamline the process and keep costs low. They are constantly evaluating build vs. buy for the tools they use in their trade. The preference is to use commercial off-the-shelf products if they are more cost-effective. This frees up their team to focus on keeping the “main thing the main thing”.
/* Begin Shameless Plug */
The whole idea of ParkMyCloud is to help out that part of the DevOps community, who run their environments in Amazon Web Services (AWS).
With ParkMyCloud, you can schedule on/off times for development, testing, QA and staging environments without AWS scripting for as little as $1-$2 per instance per month.
A number of our larger customers have walked away from their own scripted solutions to do this in favor of ParkMyCloud for a few reasons:
- It was costing their team more to maintain their AWS scripts
- The time spent working on those scripts, was time that could have been spent on mainline business applications (a huge opportunity cost)
- Their scripts provided no reporting on cost savings, so that had they no idea whether they were getting a return on their investment. (With ParkMyCloud, the payback is usually within 2-3 months.)
/* End Shameless Plug*/
/* Begin Rant */
So, I told you all of that to air a real pet peeve that I have.
Imagine my surprise when I still talk to potential customers, bent on writing their own AWS scripts to turn instances on & off. It just doesn’t make sense.
When they tell me, “Well, we can do that.” Then my response is, “Does your DevOps team also clean toilets?”
Then they give me this weird look (kind of like the look on your face right now), and respond, “Well, no.”
“Why not?” I ask. “Are they not smart enough to clean toilets?”
“Well of course they are smart enough, but it is not worth their time. We hire a janitorial service to clean our restrooms.”
“So, let me get this straight: You are enlightened enough to realize that cleaning toilets would be a waste of your team’s time, so you hired a janitorial service. Why on earth would you waste your precious DevOps resources to do the moral equivalent of this in IT, by having them waste time writing scripts to schedule on/off times for EC2 instances?”
“They should be spending that time on your main business applications. Leave that to us!”
Increasingly, they get point.
/* End Rant */
In closing, please remember: Friends don’t let DevOps friends waste time on AWS scripting for things not related to application delivery (especially when there are more cost-effective commercial products available to help save time and money). Friends do tell their DevOps friends about ParkMyCloud.