InfoQ Homepage IT Service Management Content on InfoQ
-
/articles/book-review-team-topologies/en/smallimage/Book-Team-Topologies-l-1572527747801.jpg)
Q&A on the Book Team Topologies
The book Team Topologies by Matthew Skelton and Manuel Pais shows how to arrange teams within an organization to enable effective software delivery. It describes four fundamental team types and three team interaction patterns, and dives into the responsibility boundaries of teams and how teams can communicate or interact with other teams.
-
/articles/testing-techniques-microservices-use-cases/en/smallimage/testing-microservices-part-3-logo-small-1572849393575.jpg)
Testing Microservices: Six Case Studies with a Combination of Testing Techniques - Part 3
This article presents six real world use cases of testing microservice-based applications, and demonstrates how a combination of testing techniques can be evaluated, chosen, and implemented.
-
/articles/velocity-better-metrics/en/smallimage/escaped-velocity-qa-doc-norton-s-1570774797793.jpg)
Velocity and Better Metrics: Q&A with Doc Norton
Velocity is not good for predictions or diagnostics, argued Doc Norton at Experience Agile 2019. It's a lagging indicator of a complex system which is too volatile to know what our future performance will be; it isn’t stable enough to be used reliably. We can use Monte Carlo simulation for forecasting, and cumulative flow diagrams to track work, see changes in scope, and spot bottlenecks.
-
/articles/qa-book-continuous-delivery-java/en/smallimage/continuous-delivery-java-book-logo-small-1568356698269.jpg)
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.
-
/articles/continuous-testing-best-practices/en/smallimage/unlocking-continuous-testing-logo-small-1564402385753.jpg)
Unlocking Continuous Testing: The Four Best Practices Necessary for Success
While the majority of organizations have enthusiastically embraced agile planning and development, most still find themselves unable to effectively implement continuous testing throughout the software development lifecycle. There are four best practices to help overcome this: focus on test quality, keep your tests short and atomic, test across multiple platforms, and leverage parallelization.
-
/articles/pipeline-driven-organization/en/smallimage/logo-1563354042604.jpg)
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.
-
/articles/aws-codepipeline-deploy-docker/en/smallimage/aws-codepipeline-deploy-docker-s-1557922653891.jpeg)
Deploying Docker Containers Using an AWS CodePipeline for DevOps
In this walkthrough, learn how to perform continuous integration and deployment of Docker containers with no downtime using AWS CodePipeline and Amazon Elastic Container Service (ECS).
-
/articles/devops-cloud-trends-2019/en/smallimage/devops-cloud-trends-2019-s-1550778123254.jpeg)
DevOps and Cloud InfoQ Trends Report - February 2019
An overview of how the “cloud computing” and DevOps space is evolving in 2019 including updates on Kubernetes, Chaos Engineering, Service meshes and more.
-
/articles/continuous-delivery-not-about-tech/en/smallimage/continuous-delivery-not-about-tech-s-1550010199047.jpeg)
Continuous Delivery - It’s Not All about Tech!
It’s easy to get caught up in the technical side of continuous delivery. Objectively observing all stages of the releases in action allows measuring the release process to find non-tech factors hindering your releases and the bottlenecks and queues. Make sure your communication methods are effective, and that all the people involved are genuinely working together well.
-
/articles/machine-learning-learn-devops/en/smallimage/machine-learning-learn-devops-s-1544716403154.jpeg)
What Machine Learning Can Learn from DevOps
The fact that machine learning development focuses on hyperparameter tuning and data pipelines does not mean that we need to reinvent the wheel or look for a completely new way. According to Thiago de Faria, DevOps lays a strong foundation: culture change to support experimentation, continuous evaluation, sharing, abstraction layers, observability, and working in products and services.
-
/articles/DevOps-Databases/en/smallimage/DevOps-Databases-s-1541670287515.jpeg)
How to Source Control Your Databases for DevOps
A robust DevOps environment requires having continuous integration for every component of the system. But far too often, the database is omitted from the equation. In this article, we discuss the unique aspects of databases, both relational and NoSQL, in a successful continuous integration environment.
-
/articles/service-delivery-review-missing-devops-feedback-loop/en/smallimage/service-delivery-review-missing-devops-feedback-loop-S-1540549719258.jpg)
Service Delivery Review: The Missing DevOps Feedback Loop?
This article introduces the service-delivery review and answers questions like: does the team know what their customer values about their service? How can we regularly assess service fitness?