InfoQ Homepage DevOps Content on InfoQ

  • Q&A on the Book Continuous Delivery in Java

    The book Continuous Delivery in Java by Daniel Bryant and Abraham Marin-Perez was released nearly ten years after the original Continuous Delivery book by Dave Farley and Jez Humble, and more than 20 years after Java’s first release. Q&A with the authors to better understand from their experience why a book on Continuous Delivery specifically for Java and the JVM ecosystem was needed.

  • How to Use Chaos Engineering to Break Things Productively

    Chaos can be a preventative for calamity. It's predicated on the idea of failure as the rule rather than the exception, and it led to the development of the first dedicated chaos engineering tools. This article explores chaos engineering, and how to apply it.

  • Designing Chaos Experiments, Running Game Days, and Building a Learning Organization: Chaos Conf Q&A

    The second Chaos Conf event is taking place in San Francisco over 25-26 September. In preparation for the conference, InfoQ sat down with a number of the presenters, and discussed topics such as the evolution and adoption of chaos engineering, key people and process learning from running chaos experiments, and what the biggest blockers are for mainstream adoption.

  • How Compuware Escaped Its Waterfall for True Mainframe DevOps

    Compuware fought gravity and began innovating using DevOps, without losing staff or focus on the mainframe computing platform that brought company success for over 45 years.

  • An Engineer’s Guide to a Good Night’s Sleep

    Increased microservices adoption, fueled by the move to the cloud where architectures and infrastructure can flex and be ephemeral, adds complexity every day to the systems we create and maintain. This takes place alongside operating models with autonomous and totally empowered teams, so each distributed system has its own tapestry of technical approaches, languages, and services.

  • Kubernetes Workloads in the Serverless Era: Architecture, Platforms, and Trends

    Explore how microservices architecture has evolved into cloud-native architecture, where many of the infrastructure concerns are provided by Kubernetes in combination with additional abstractions provided by service mesh and serverless frameworks. In addition, the serverless ecosystem is evolving by exploring standard and open packaging, runtimes, and event formats.

  • Running Single-file Programs without Compiling in Java 11

    Starting with Java SE 11, and for the first time in the programming language’s history, you can execute a script containing Java code directly without compilation. The Java 11 source execution feature makes it possible to write scripts in Java and execute them directly from the *inx command line.

  • The Pipeline Driven Organization - Enabling True Continuous Delivery

    Many organizations try to implement continuous integration or continuous delivery, but they get stuck in the process; too many human bottlenecks standing between the pipelines. By teaching pipelines to make better decisions and offloading human judgements onto the pipelines we can have the pipelines make decisions all the way up to production to create a true continuous delivery mechanism.

  • How to Seamlessly Evolve DevOps into DevSecOps

    As DevOps evolved, it became obvious that it was about more than just software development and operations management. With each new story of a massive data breach and its catastrophic consequences, cybersecurity swiftly became recognized as a critical part of any IT ecosystem. This realization led to DevSecOps. This article looks at how to embrace a DevSecOps approach.

  • NotPetya Retrospective

    As we hit the second anniversary of NotPetya, this retrospective is based on the author’s personal involvement in the post-incident activities. In the immediate aftermath, it seemed like NotPetya could be the incident that would change the whole IT industry, but it wasn’t—pretty much all the lessons learned have been ignored.

  • Sustainable Operations in Complex Systems with Production Excellence

    Successful long-term approaches to production ownership and DevOps require cultural change in the form of production excellence. Teams are more sustainable if they have well-defined measurements of reliability, the capability to debug new problems, a culture that fosters spreading knowledge, and a proactive approach to mitigating risk.

  • A Different Meaning of CI - Continuous Improvement, the Heartbeat of DevOps

    This personal experience report shows that political in-house games and bad corporate culture are not only annoying and a waste of time, but also harm a lot of initiatives for improvement. Whenever we become aware of the blame game, we should address it! DevOps wants to deliver high quality. The willingness to make things better - products, processes, collaboration, and more - is vital.


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.