5 Things You Should Know About Continuous Deployment…by the Man Who Coined the Term
Tech Guru Timothy Fitz on making the jump to Continuous Deployment, the buzz around DevOps, and why GitHub has set back Software Departments by 5-10 years…
BlazeMeter invited me to ask 5 key questions to Timothy Fitz – the man who coined and popularized Continuous Deployment. Here are the results:
How would you define continuous deployment and how is it different to continuous delivery?
Timothy Fitz: This is a great question that isn’t frequently asked, since it is often assumed that they both mean the same thing. Usually, when people refer to continuous delivery, they actually mean continuous deployment.
(more…)
The rapid development of SaaS applications in the cloud means more and more people, features and open source applications are combining together into one huge platform. Due to the immediacy of software development, a major challenge for software vendors is to audit changes in their application environments, such as system configurations. The problem is that any `change performed at any stage of an operation can impact other areas of an application. This digital butterfly effect can be very detrimental in today’s fast-paced, on-demand environment. It becomes even more destructive when these changes can’t be found, due to inadequate tracking. Failure to track changes, can greatly affect a company’s revenues and success.
The cloud has allowed modern, web-scale IT companies, like Airbnb and Netflix, to grow and flourish into booming enterprises all over the web. With its flexibility and efficiency, it supports the demand of an organization’s growth from zero to millions of users, allowing them to prepare for this potential growth, as well. Before the cloud, simulating millions of concurrent users and running scalability, stress, or stability tests was very hard to implement, if not impossible. Cloud technology has brought software testing, especially performance testing, to a whole new playing field.
