How can you tell if a DevOps initiative is succeeding? After all, there are no standardized benchmarks. Savaram Ravindra explains what kind of metrics you should measure your DevOps approach to and judge its success that way.
We’re gearing up for JAX DevOps by talking to Kris Buytaert, who explains what he means by “software has only value when it is running in production”.
The same marketing hype that surrounded “Agile” has now switched to “DevOps”; the combination of the two is one way to solve all the issues that IT organizations have been known for. This has generated the chimera of the “full stack” developer, which simply means that now a developer is expected to do it all. What else could it mean?
DevOps has arrived as a legitimate and mainstream means of delivering business value with IT. But by no means has the DevOps concept stopped changing. Kurt Milne examines the DevOps trends that are already on their way.
Hoshin Kanri is a Japanese managerial process that DevOpsDays London organiser Barry Chandler has recently discovered, and he wants the world to know how teaming it with DevOps can mean great things for enterprise organisations.
The transition to DevOps for many companies has been a successful move. However, now that the processes between development and operations are getting an overhaul, corporate culture has been left to its own, resulting in many burnt out developers.
The positive change that DevOps brings for enterprise IT is becoming more and more obvious. And yet DevOps success doesn’t come easily. When it comes to implementing a DevOps approach together with Continuous Delivery, the key to success is trust and visibility.
Microservices are great – we can all agree. But there’s no doubting what level of complexity they bring to IT systems. “The problem is, we don’t understand the problem,” quotes software architect Peter Elger, who shows us the ways to fail fast and iterate rapidly with microservices.
DevOps is cool. Correction: DevOps is mainstream. Correction: DevOps has broken through the mainstream and is now quickly catching up on “Agile”, “Big Data” and the almighty “Cloud” as an excessively used buzzword. So how much substance is there to the hype of DevOps?
Are the promises of microservice heaven true? Are they better than monoliths in every way? And does a distributed system save money? We report on the latest advice of various microservices experts speaking at the W-JAX 2015.
Microservices are mainstream, security needs to be talked about more and development and operations should be best friends. Daniel Bryant, Principal Consultant at OpenCredo, shares the lessons he’s learnt from attending the JAX London 2015.
Conversational practices like DevOps can enable organisations to practice empathy by detecting and narrowing the gap between their customers and their understanding of them, says Jeff Sussna. With that, he revisits the essence of DevOps in empathy.
DevOpsCon 2015 speaker Walid Farag gives us an in-depth look into the modern datacenter by harnessing IT operations processes and tying it all with the bigger picture. He looks to answer the following question: Why choose business agility?
Pierre Fricke is back to discuss DevOps and its role in what he is the calling the battle between the creative developers and the process junkies. What will the future bring for the role of DBAs?