Continuing to where we left in the last
post are next two principles of DevOps.Continuous Testing /Continuous
Monitoring which are facilitated by continuous integration .
Continuous Testing
Continuous Integration and Delivery are
both (almost) meaningless without Continuous Test. Not having
motoring and hence, not knowing how the application is performing in
production makes the whole process of DevOps moot. What good is
having an streamlined Continuous Delivery process is the only way you
find out about your applications’ functionality or performance
being below par is via a ticket opened by a disgruntled user?
Continuous testing reduces the cost of
testing while helping development teams balance quality and speed. It
eliminates testing bottlenecks through virtualized dependent
services, and it simplifies the creation of virtualized test
environments that can be easily deployed, shared, and updated as
systems change. These capabilities reduce the cost of provisioning
and maintaining test environments, and they shorten test cycle times
by allowing integration testing earlier in life cycle.
Continuous Monitoring
In Production, the Ops team manages and
ensures that the application is performing as desired and the
environment is stable via Continuous Monitoring. While the Ops teams
have their own tools to monitor their environments and systems,
DevOps principles suggest that they also monitor the applications.
They need to ensure that the applications are performing at optimal
levels – down to levels lower than system monitoring tools would
allow. This requires that Ops teams use tools that can monitor
application performance and issues. It may also require that they
work with Dev to build self-monitoring or analytics gathering
capabilities right into the applications being built. This would
allow for true end-to-end monitoring – continuously.
Putting The Four Continuous principles
of devops
- Continuous Integration
- Continuous Delivery
- Continuous Testing
- Continuous Monitoring
No comments:
Post a Comment