InfoQ Homepage DevOps Content on InfoQ
-
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.
-
Towards a Unified, Standard API for Consolidating Service Meshes
Service mesh architectures enable a control and observability loop. At the moment, service mesh implementations vary in regard to API and technology, and this shows no signs of slowing down. Building on top of volatile APIs can be hazardous. Here we suggest to use a simplified, workflow-friendly API to shield organization platform code from specific service-mesh implementation details.
-
How to Mitigate the Pain of Getting and Giving Feedback
Companies that encourage open and honest feedback do better than companies that do not. Nonetheless, giving feedback is difficult because social and physical pain share some of the same neural circuitry. Hence, feedback can feel physically painful, as Sarah Hagan discusses in her 2018 QCon San Francisco talk . Hagan uses scientific research to demonstrate how to give feedback properly.
-
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).
-
The Potential for Using a Service Mesh for Event-Driven Messaging
In this article, we discuss one of the most challenging and unexplored areas in service mesh architecture; supporting event-driven messaging. There are two main architectural patterns that we discuss here: the protocol proxy sidecar, and the HTTP bridge sidecar. Regardless of the pattern that is used, the sidecar can facilitate features such as observability, throttling, tracing etc.
-
API Gateways and Service Meshes: Opening the Door to Application Modernisation
Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.
-
Q&A on the Docker on Windows – Second Edition
InfoQ interviewed Elton Stoneman about the significant changes in the 2nd edition of Docker on Windows, typical use-cases, benefits of CI/CD Pipelines, containerization, guidance, operations, and collaboration between Microsoft and Docker.
-
To Multicluster, or Not to Multicluster: Inter-Cluster Communication Using a Service Mesh
Communication within Kubernetes clusters is a solved issue, but communication across clusters requires more design and operational overhead. Before deciding on whether to implement multicluster support, you should understand your communication use case.
-
Linkerd v2: How Lessons from Production Adoption Resulted in a Rewrite of the Service Mesh
Linkerd 2.0 introduced a substantial rewrite of the widely adopted service mesh, using a split between Go and Rust. In this article, we discuss the lessons learned in the "cauldron of production adoption", and how those lessons became the basis of Linkerd 2.x’s philosophy, design, and implementation.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Application Performance Management in the Microservices Age
Manual Monitoring – Bad! Automatic Monitoring – Good!
Application Performance Management in a Containerized World
Open Source Microservices Monitoring is a Terrible Idea
Yes Virginia, Automatic Monitoring DOES Exist
Finding the Needle in the Containerized Haystack
The Ultimate Application Monitoring Guide for Kubernetes
