Find videos, customer case studies, datasheets, whitepapers and more to learn how Commvault can help you make your data work for you.
Speed. Agility. Flexibility. These are the big drivers behind most organizations’ move to the cloud for their test/dev environments. Freed from the shackles of physical, on-premises infrastructures means test/dev teams can be incredibly fast both in standing up and tearing down test beds. They can manage version control. And they can share work between teams faster than ever before. Ultimately, this means the business can respond faster to the rapidly changing needs of customers.
“The cloud is quickly growing… to becoming a real production-level environment,” says Phil Goodwin, Research Director at IDC. “That transition requires cost-effective and efficient access, through the type of capabilities Commvault® is debuting, to accelerate data cloud recovery and migration.”
Here are five ways in which the cloud makes sense for test/dev.
ONE: SHARING ENVIRONMENTS
To develop and test software for particular environments, programmers need access to a wide variety of development, staging, and production environments. These may require different kinds of processors, multiple operating systems and other software, different kinds and amounts of
storage, and so on.
But in an organization with many programmers – particularly if the programmers are global – it can be challenging, not to mention expensive, to provide identical development and test beds around the world for all the programmers who might be working on them. The problem is, if the programmers aren’t working on identical environments, it becomes difficult to track down bugs and accurately test performance.
The cloud can have all the resources that the programmers need, and they can get access to it from anywhere. Not to mention, as businesses increasingly move to the cloud, developers and testers need to make sure their applications run on various vendors’ implementation of the cloud as well. And with cloud locations all over the world, developers worldwide can ensure that they’re running on hardware close to them, to reduce latency time and for data sovereignty.
TWO: SHARING RESOURCES
While developers and testers need access to many kinds of resources, especially when they’re testing the scalability of an application, they don’t always need all of them all of the time. That means a lot of expensive hardware and software has to be bought to have around for when the programmers do need it. But the rest of the time, it means unused capacity is often sitting around going to waste – all of it also needing regular maintenance and updates.
The cloud gives programmers access to a centralized pool of resources when they need them. That way, other programmers use them when they’re not needed, without having to fight for limited resources, and you only pay for the resources your team is actually using.