The role of open-source software in DevOps, the cautionary tale of the Heartbleed bug, and why a mixed open-source and commercial software strategy is your route to low-risk growth.
Listen to some DevOps evangelists talk, and you would get the impression that IT operations teams exist only to serve the needs of developers. Don't get me wrong, software development is a good competence to have in-house if your organisation depends on custom applications and services to differentiate its business.
DevOps is one of the current catchphrases within the development industry. Not surprisingly, however, there are several conflicting thoughts as to what DevOps constitutes other than effective and improved collaboration of operations and development teams within an organization.
Even though the definition of DevOps may differ to different organizations, there is a list of best practices aimed at enhancing collaboration in order to come up with better software. This article discusses a few of these best practices examined from the developer and operation team’s perspective.
Embracing automation, innovation, wider communication, clarity and being open to change are keys for software security personnel that DevOps learned long ago.