Three DevOps Predictions for 2017 by CA Technologies
Continuous testing, security of code, and metrics pegged as hottest trends in
DevOps this year
SINGAPORE, 17
January, 2017 – CA
Technologies (NASDAQ: CA) today announced three trends in DevOps it expects
will come under the organizational spotlight in 2017. DevOps removes the silos
between the development and operations teams, advocating better communication
and collaboration between the two units so organizations can achieve greater
digital agility.
January, 2017 – CA
Technologies (NASDAQ: CA) today announced three trends in DevOps it expects
will come under the organizational spotlight in 2017. DevOps removes the silos
between the development and operations teams, advocating better communication
and collaboration between the two units so organizations can achieve greater
digital agility.
Interestingly, the key trends surrounding
DevOps this year are not specifically about development or operations, but will
instead be on testing, security, and metrics.
DevOps this year are not specifically about development or operations, but will
instead be on testing, security, and metrics.
“As organizations race to deliver innovations to market, they will find that
ensuring the quality, security and performance of their applications are just
as important as speed. DevOps plays a pivotal role in making sure these happen
as businesses put software at the core of their DNA to survive and thrive in
today’s application economy,” said Richard Gerdis, Vice President, DevOps, Asia
Pacific & Japan, CA Technologies.
Here are the three hottest DevOps trends as
predicted by CA:
predicted by CA:
1. Continuous testing to
become a topic of interest
become a topic of interest
Rapidly promoting new code into production fuels
the need for speed, but this can also be a fast track to digital failure. An
accelerated pace of development puts pressure on the testing function,
relegating it to a single phase within the software development lifecycle
(SDLC). This is insufficient as customer expectations of digital experiences
tend to escalate over time, rendering existing code not good enough.
the need for speed, but this can also be a fast track to digital failure. An
accelerated pace of development puts pressure on the testing function,
relegating it to a single phase within the software development lifecycle
(SDLC). This is insufficient as customer expectations of digital experiences
tend to escalate over time, rendering existing code not good enough.
The only way to produce good, quality code is to
test it rigorously, and more importantly, to test it throughout the DevOps
lifecycle. Testing can no longer be the job of quality assurance (QA) engineers
alone, developers need to be able to test code and make the test results also
available to operations.
test it rigorously, and more importantly, to test it throughout the DevOps
lifecycle. Testing can no longer be the job of quality assurance (QA) engineers
alone, developers need to be able to test code and make the test results also
available to operations.
2. Development,
security, and operations will unify to become DevSecOps
security, and operations will unify to become DevSecOps
Security is likely to continue being an
important topic this year, given the growing intensity and sophistication of
cyber threats. In addition to speed and quality, good code also needs to
protect users against cyber-malice, and organizations from negative publicity
and reputational damage.
important topic this year, given the growing intensity and sophistication of
cyber threats. In addition to speed and quality, good code also needs to
protect users against cyber-malice, and organizations from negative publicity
and reputational damage.
For code to be safe, it must be deployed within
a solid security architecture. Security validation should be viewed as a
special case of testing, as the requirements of security-related code testing
are unique and dynamic, as well as involve experts and constituencies not
usually included in the DevOps process.
a solid security architecture. Security validation should be viewed as a
special case of testing, as the requirements of security-related code testing
are unique and dynamic, as well as involve experts and constituencies not
usually included in the DevOps process.
3. Increasing focus on DevOps metrics
Until recently, very few organizations have
paid attention to DevOps metrics. After all, it can be tough to get basic
DevOps processes, tools and culture in place. However, it is difficult to
improve what cannot be measured, which is why the adoption and standardization
of DevOps success metrics are likely to gain ground this year.
paid attention to DevOps metrics. After all, it can be tough to get basic
DevOps processes, tools and culture in place. However, it is difficult to
improve what cannot be measured, which is why the adoption and standardization
of DevOps success metrics are likely to gain ground this year.
Metrics, both collective and individual, can
improve digital practices in many ways. Collective metrics can discover
bottlenecks in processes and optimize resource allocation. Individual metrics
can pinpoint coaching needs and replicate good performance. With this variety
of benefits, it is highly plausible that the industry will concur on a common
set of metrics this year.
improve digital practices in many ways. Collective metrics can discover
bottlenecks in processes and optimize resource allocation. Individual metrics
can pinpoint coaching needs and replicate good performance. With this variety
of benefits, it is highly plausible that the industry will concur on a common
set of metrics this year.
For the LATEST tech updates,
FOLLOW us on our Twitter
LIKE us on our FaceBook
SUBSCRIBE to us on our YouTube Channel!