Weekly Top 10: Keeping the DevOps Pulse on Teams, Testing and Innovation
Some great links from around the Internet on DevOps best practices.
Join the DZone community and get the full member experience.Join For Free
If there is one thing that remains constant, it is that DevOps is a practice – one that will be continually improved upon. This week’s top news prove that DevOps is maturing, as it reaches farther into the enterprise and the mainstream. As DevOps practices progress over time, so do the people involved. An emphasis on culture, teams and collaboration has grown naturally out of the DevOps movement, and this emphasis has become a major tenet (and oftentimes a challenge). This week, we read about empowering teams to breedinnovation in the enterprise, how testing is shaping the team and how it also plays into the role of automation. Continue reading for more on the latest DevOps news and trends, and, as always, stay tuned to all the news coming from @ElectricCloud on DevOps andContinuous Delivery throughout the week.
1) Catch a Wave: Optimizing the Transformation to a DevOps Mainstream
By Yaniv Yahuda | Published on @DZone
Mark Samuels writes in ZDNet on how CIOs can make the most of an industry trend toward DevOps management. As a “much-hyped methodology” centered on “cooperation and collaboration between software developers and other more operationally-focused IT professionals,” DevOps allows for “continually evolving services that closely match business demands.
2) How to Bring DevOps Practices to Legacy Applications (#c9d9 – Continuous Discussions)
By @arora_tarun | Published on Visual Studio Geeks
Recently I participated in an online panel to discuss how best to tackle Continuous Delivery for Legacy Applications. This was one in the series of Continuous Discussions (#c9d9). #c9d9 is a series of community panels about Agile,Continuous Delivery and DevOps. Read on for some of the key points that emerged in this discussion… Feel free to leave a comment if you have any suggestions of your own…
3) Driving Innovation With Your Teams
In last month’s blog I talked about how to keep your C-Suite in the fast lane. What about the rest of the organization? How do you drive a culture of innovation throughout your business? Everyone is vying to create a collaborative workspace; bright colors, comfortable seating, and even free food. But what does it take to truly enculturate innovative start up thinking deep into your organization and why is it important?
4) 9 Ways DevOps and Automation Bolster Security, Compliance
Information security and compliance are critical to businesses across the globe, especially given past examples of data breaches and looming cybersecurity threats. Yet InfoSec has long been thought of as the group that slows things down, the wet towel to your DevOps efforts, often requiring a more conservative approach as a means of mitigating risk. Traditionally, DevOps has been viewed as a risk by InfoSec teams, with its increased velocity of software releases seen as a threat to governance and security and regulatory controls (which, by the way, often require the separation of duties, rather than the breaking of silos).
5) Optimize DevOps With Self-Contained Containers
Keeping a software application up and running is a challenging task. The operations engineers responsible for maintaining back-end infrastructure have a difficult job, and it’s even more challenging when each change the developers want to roll out requires changes to the infrastructure and its configuration. Recently, though, many organizations have begun to adopt container technology as a consistent, pre-configured delivery mechanism that makes deployment simpler and less error-prone.
6) Citizen Developers: Low Code is Now Enterprise-Class
The central feature that all low code platforms share is an environment where non-technical business users can create and modify business applications. In the large enterprise environment, however, none of these vendors expect business users to perform all the tasks necessary to build and maintain the apps they have a hand in building.
7) Private Cloud: Is the Term Just Being Used a Fig Leaf?
By Moshe Kranc | Published on @ITProPortal
One of the perks of my job is that I get to talk with IT thought leaders across various business domains. Lately, in talking with IT managers in the financial sector, I have observed a common thread: they sometimes mistakenly refer to any shared infrastructure as a ‘private cloud’.
8) Organizing the Test Team
By Sanjay Zalavadia | Published on @InfoQ
Twenty years ago, when software shipped in boxes, there was a standard organization for software groups: a development organization, a test organization, and a documentation organization, each of roughly the same size. We’ve come a long way since those days, separating management work from product ownership, including analysts, creating usability and user experience roles and downplaying the role of the documentation. Very few of the companies we work with, sell software in boxes at stores and it is rarer still to see the CD duplication and shipping process as part of a project.
9) Automated Testing for the Internet of Things
By @vassvdm | Published on Nordic APIs
The Internet of Things (IoT) is upon us. Every object you see around you — whether it’s your fridge, your electric toothbrush, your car, even your clothes, are about to acquire a form of sentience. Some of them already have. Fitbit watches, Nest thermostats and Apple TVs are just the tip of the iceberg when it comes to our embedded future. Sensors, embedded systems and cloud backends are coming together to bestow smartness upon a bewildering array of previously inanimate, dumb objects.
10) Agile is Too Slow: Why You Should Try Continuous Deployment
At enterprise translation platform Smartling, developers strive for continuous deployment, rather than a six-month waterfall, or even two-week agile cycle. But why is this better? And how do they actually make it work? In the second part of a two-part interview with The Enterprisers Project, CTO Andrey Akselrod provides some answers.
Opinions expressed by DZone contributors are their own.