chapter
Let the traditional waterfall model of software development and DevOps model compares to understand the changes brought about DevOps.
Suppose an application program in 2 weeks on the line, and the code is written 80%. Assuming that the application is a new project, the purchase and deployment of server started:
|
|
|
| After ordering a new server, the development team will be tested, operation and maintenance team deployed a large number of documents related to work. | After ordering a new server, development, and operation and maintenance team will work together to complete the deployment of the relevant paperwork. This will improve the transparency of infrastructure needs. |
| About failover, redundancy forecast, data center and storage requirements of the position is not accurate, because a deep understanding of the application developers can not provide input. | Since the input of developers, on failover, redundancy, disaster recovery, data center locations and predict storage needs very accurate. |
| Operation and maintenance team knew nothing about the progress of the development team. Operation and maintenance team to develop surveillance plans based on their own understanding. | In DevOps mode, operation and maintenance team fully informed of the progress developers. Operation and maintenance team to interact with the developers, to develop monitoring plans to meet IT and business needs, in addition to the use of advanced application performance monitoring (APM) tool |
| Before put into use, stress testing make the application to crash. Published likely to be postponed. | Before put into use, stress testing make the application slower. The development team quickly repaired the bottleneck, the application will be released on time. |