InfoQ Homepage DevOps Content on InfoQ
-
/articles/continuous-improvement-heartbeat-devops/en/smallimage/continuous-improvement-heartbeat-devops-s-1558624249506.jpeg)
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.
-
/articles/service-mesh-api-federating/en/smallimage/service-mesh-api-federating-s-1558080393545.jpeg)
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.
-
/articles/mitigate-pain-getting-giving-feedback/en/smallimage/mitigate-pain-getting-giving-feedback-s-1558074717961.jpeg)
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.
-
/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/service-mesh-event-driven-messaging/en/smallimage/using-service-mesh-for-event-driven-messaging-logo-small-1557145841741.jpg)
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.
-
/articles/api-gateway-service-mesh-app-modernisation/en/smallimage/api-gateway-service-mesh-app-modernisation-s-1556793369643.jpeg)
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.
-
/articles/book-docker-windows-second-edition/en/smallimage/docker-on-windows-s-1556625976961.jpeg)
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.
-
/articles/kubernetes-multicluster-comms/en/smallimage/kubernetes-multicluster-comms-s-1555590645353.jpeg)
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.
-
/articles/linkerd-v2-production-adoption/en/smallimage/linkerd-v2-production-adoption-s-1554326459659.jpeg)
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.
-
/articles/cloud-live-migration/en/smallimage/cloud-live-migration-s-1553699349875.jpeg)
Sleeping Well at Night During a Live Cloud Migration in a VMware Environment
This article describes the challenges of live migration to the cloud and presents key concepts and requirements that enterprises and their service providers need to understand and adopt if they want to sleep well at night when migrating on-premises VMs and data to the cloud.
-
/articles/improving-cloud-security/en/smallimage/improving-cloud-security-s-1553193784100.jpeg)
Seven Steps for Improving Cloud Security with Business Integration
For business owners and information technology professionals, cloud computing has represented a significant advancement in terms of efficiency and supportability. But like with any major shift in the IT industry, the cloud brings a host of new security risks. Let’s take a look at the most common risks associated with integrating cloud-based business systems and how to manage them appropriately.
-
/articles/culture-methods-trends-2019/en/smallimage/icon-trends-final-1552550485795.jpg)
Culture & Methods – the State of Practice in 2019
The latest Culture and Methods Topic Graph shows the topics that the editorial team feels are gaining traction and should be explored at the beginning of 2019.