InfoQ Homepage Continuous Delivery Content on InfoQ
-
Compromised GitHub Action Highlights Risks in CI/CD Supply Chains
The popular tj-actions/changed-files GitHub Action used by thousands of repositories recently compromised those repositories, exposing a critical weakness in how open-source Actions are published and consumed.
-
Flux v2.5 Release: Expanding GitOps Capabilities with CEL Integration and GitHub App Auth
Flux, the popular GitOps tool for Kubernetes, has released version 2.5, bringing a host of powerful new capabilities that significantly enhance its functionality and flexibility. This release represents a substantial evolution in Flux's capabilities, with features that the community has been eagerly awaiting. Let's explore what's new and how these changes can improve your GitOps workflows.
-
Most Companies Experience Weekly Outages: The State of Resilience 2025 Report
According to The State of Resilience 2025 Report, published by Cockroach Labs, outages are commonplace in most organizations, with 55% of companies reporting weekly and 14% reporting daily outages. Staggering 100% of survey participants experienced revenue losses due to outages, with some companies (8%) reporting losses of USD $1 million or higher over the last 12 months.
-
Microsoft Announces General Availability of Fabric API for GraphQL
Microsoft has launched Fabric API for GraphQL, moving the data access layer from public preview to general availability (GA). This release introduces several enhancements, including support for Azure SQL and Fabric SQL databases, saved credential authentication, detailed monitoring tools, and integration with CI/CD workflows.
-
No EC2 or Kubernetes Allowed: Insights from Building Serverless-Only Architecture at PostNL
PostNL shared insights and guidance from its transition from outsourced IT project delivery to an in-house product delivery capability. By embracing cloud-native technologies, with an emphasis on serverless services, the company achieved significant gains in productivity and market responsiveness while reducing operational costs.
-
Planning, Automation and Monorepo: How Monzo Does Code Migrations Across 2800 Microservices
Monzo products are supported by an extensive microservice-based platform of over 2800 services. The company relies on planning and heavy automation to drive code migrations at scale and leverages config service to support gradual roll forwards and quick rollbacks in case of issues. Migrations are managed by a central team rather than service owner teams to avoid delays and inconsistencies.
-
Enabling Fast Flow in Software Organizations
Resolving impediments to flow and removing unnecessary sources of cognitive load can make culture issues disappear in organisations, Nigel Kersten argued. Start with a clear strategy that is easy to communicate, then follow the path to creating stream-aligned teams and platform teams, he suggested.
-
Experiences from Doing DORA Surveys Internally in Software Companies
Doing DORA surveys in your company can help you reflect on how you are doing software delivery and operation. The way you design and run the surveys, and how you analyze the results, largely impact the benefits that you can get out of them. Carlo Beschi shared his experiences from doing DORA surveys at Agile Cambridge.
-
AWS CodePipeline Embraces Monorepos, GitFlow and Branches
AWS has announced new features in CodePipeline, their managed continuous delivery service facilitating automated release pipelines for application and infrastructure updates. These additions aim to support teams employing various delivery strategies, providing customers with more flexibility in their pipeline designs.
-
Booking.com Doubles Delivery Performance Using DORA Metrics and Micro Frontends
The team in Booking.com’s fintech business unit implemented a series of improvements across the backend and the frontend of its platform and was able to double the delivery performance, as measured by DORA metrics. Additionally, the Micro Frontends (MFE) pattern was used to break up the monolithic FE application into multiple decomposed apps that could be deployed separately.
-
Descaling for Delivery and Using AI to Enhance Software Development: Learnings from QCon New York
The track Optimizing Teams for Fast Flow - Surviving in the Post-agile Aftermath at QCon New York 2023 comprised two talks in the morning that went into replacing an agile process with engineering and conversational software delivery using AI.
-
Rebecca Parsons - Thoughtworks CTO: by 2025 We'll See Evolution in Architecture, But Not Revolution
On the second day of the QCon London conference, Rebecca Parsons, chief technical officer at Thoughtworks, revisited the idea of evolutionary architecture imaging how it might evolve until 2025. Starting from the definition, she visited each of the definitory attributes anticipating how they will evolve in the next period. Concluding that we will see evolution, but not a revolution.
-
Amazon ECS Adds Automated Rollbacks
Amazon has released native support for automated rollbacks within their Amazon ECS service. This feature leverages Amazon CloudWatch metric alarms to monitor and, if necessary, reverts the in-progress deployment. This feature supports using any system metrics that CloudWatch Container Insights collects for Amazon ECS as well as custom metrics.
-
Reliable Continuous Testing Requires Automation
Automation makes it possible to build a reliable continuous testing process that covers the functional and non-functional requirements of the software. Preferably this automation should be done from the beginning of product development to enable quick release and delivery of software and early feedback from the users.
-
Slack Implements Circuit Breakers to Improve CI/CD Pipeline Availability
Slack recently published how it implemented the Circuit Breaker pattern to improve its CI/CD pipeline availability. Before this project, engineers at Slack saw challenges as peak request volumes in internal tooling caused cascade failures in dependent systems. Since completion, engineers saw increased service availability and fewer bad developer experiences like flakiness from failing services.