Weekly Top 10: How to Make the Most of DevOps
Weekly Top 10: How to Make the Most of DevOps
This review of the week's news in DevOps topics touches on the future of DevOps, self-healing service management, automated CD/CI, and more.
Join the DZone community and get the full member experience.Join For Free
The original post lives on the Electric Cloud blog.
Welcome to another round-up of the latest news in DevOps, Agile and Continuous Delivery. In this week’s post, DevOps proves it’s here to stay, as 50% of tech leaders are now implementing DevOps – which has been proven to increase speed of software delivery while maintaining quality – saving organizations time and money. Also in this week’s news, we revisit some best practices for Continuous Delivery and find out what’s in store for DevOps in the foreseeable future.
Continue reading for more on the latest modern software delivery news and trends, and, as always, stay tuned to all the news coming from @ElectricCloud on DevOps and Continuous Delivery throughout the week.
1) DevOps: Where It’s Going and How to Make the Most of It
DevOps is much more than a set of practices for smarter software development. The benefits of Agile-type thinking — such as iterative development and continuous delivery — are being pushed beyond the IT department and out into the wider business. Here’s how adopting small, quick changes will deliver new benefits to businesses and their customers in the future.
2) CIO Jury: 50% of Tech Leaders Are Implementing DevOps
Organizations including Adobe, Amazon, Target, and Walmart have adopted the DevOps workflow to improve productivity and communication. In terms of other organizations, DevOps implementation is currently “all over the map,” Jeff Sussna, founder and principal of Ingineering.IT and author of Designing Delivery: Rethinking IT in the Digital Service Economy, told ZDNet.
3) Self-Healing Service Management and the Future of DevOps
By Chris Tozzi | Published on @devopsdotcom
How can DevOps teams take continuous delivery to the next step? Part of the answer lies in self-healing, which could optimize performance management and monitoring and underpin the software delivery pipelines of the future. Self healing means the ability of systems or environments to detect and resolve problems automatically. It eliminates the need for manual human intervention, upon which most systems today still rely to fix issues.
4) Victory! The Smell of Skunkworks in Your Office in the Morning
While it’s easy to start up a few, flashy new DevOps teams, releasing to production each week and flaunting the ball-and-chain of enterprise governance, scaling that change to your organization will always be challenging, if not crushingly impossible. When it comes to scaling the skunk-works, I’m reminded of a conversation with a struggling enterprise architect. I often use the company’s mobile app and it’s updated frequently, integrated well with iOS, and provides an overall very pleasant experience. Such results are normally unexpected from this type of aged, highly regulated, lumbering enterprise.
5) DevOps, Invest For Velocity And Quality!
Delivering exceptional customer experiences and product for your business take speed and flexibility. More than ever before, speed and flexibility are required from every part of your organization, business and IT alike. DevOps provides your business leaders, enterprise architects, developers and I&O leaders a philosophy to achieve, not only the velocity that customers desire but also drive innovation and enforces quality. One example is ING. The company is undergoing a major digital transformation in which DevOps is a primary driver supporting their transformation.
6) Continuous Delivery: 7 Hard-Earned Lessons for Getting it Right
It seems laughable now, but do you remember when Internet Explorer was updated every two years? Times have changed. Development cycles are approaching warp speed as companies deal with the competitive pressure to update their applications and websites as frequently as possible.
7) Does IT Industry Need Better Namings?
By @ionutbalosin | Published on @InfoQ
After reading plenty of articles, books and listening to conference speakers, I often ask myself if we are always using appropriate or consistent terms in IT industry. We have borrowed some of them from other domains, which is a fairly good approach, but sometimes we distort their meanings or use terms in an inconsistent way, within IT and also in comparison to other disciplines.
8) Getting Your DevOps On: DevOps 101
By Matt Brewster | Published on @TechSpective
DevOps—a cross-disciplinary, collaborative practice that blends software development and information technology operations—aims to build, test, and deliver software both more quickly and reliably. It involves the entire project lifecycle, from the early stages of planning through production support efforts. The “Dev” in DevOps relates to the development of the product—including varied disciplines such as QA and product teams—while the “Ops” in DevOps involves disciplines such as security professionals, system administrators, and operations teams.
9) Why Automated Continuous Integration is a Must for Microservices Success
Docker containers and microservices are appealing to DevOps teams with tight deadlines, but it’s a very bad idea to use either without automated continuous integration and testing in the house, according to Jim Rose, CEO of CircleCI, a software-as-a-service continuous integration platform provider based in San Francisco.
10) Examining The Internals Of A Serverless Platform: Moving Towards A ‘Zero-Friction’ PaaS
By Eliraz Busi | Published on @TechBeaconCom
Managing and controlling the process of continuous integration (CI), especially with modern methodologies such as agile that emphasize fast delivery, is one of the biggest challenges software companies experience. Doing so successfully requires collaboration between many different stakeholders.
Published at DZone with permission of Anders Wallgren , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.