Let's compare traditional software waterfall model with DevOps to understand the changes DevOps bring.
We assume the application is scheduled to go live in 2 weeks and coding is 80% done. We assume the application is a fresh launch and the process of buying servers to ship the code has just begun-
| After placing an order for new servers, the Development team works on testing. The Operations team works on extensive paperwork as required in enterprises to deploy the infrastructure. | After placing an order for new servers Development and Operations team work together on the paperwork to set-up the new servers. This results in better visibility of infrastructure requirement. |
| Projection about failover, redundancy, data center locations, and storage requirements are skewed as no inputs are available from developers who have deep knowledge of the application. | Projection about failover, redundancy, disaster recovery, data center locations, and storage requirements are pretty accurate due to the inputs from the developers. |
| Operations team has no clue on the progress of the Development team. Operations team develop a monitoring plan as per their understanding. | In DevOps, the Operations team is completely aware of the progress the developers are making. Operations team interact with developers and jointly develop a monitoring plan that caters to the IT and business needs. They also use advance Application Performance Monitoring (APM) Tools |
| Before go-live, the load testing crashes the application. The release is delayed. | Before go-live, the load testing makes the application a bit slow. The development team quickly fixes the bottlenecks. The application is released on time. |
No comments:
Post a Comment