InfoQ Homepage Continuous Integration Content on InfoQ
-
Backend FinOps: Engineering Cost-Efficient Microservices in the Cloud
Backend FinOps integrates financial discipline into microservices, crucial for cutting cloud costs. Challenges such as resource fragmentation and cold starts underscore the need for intelligent design, effective language choice, robust tagging, and automation. Implementing FinOps via IaC, CI/CD checks, and dynamic autoscaling (e.g., Karpenter) ensures sustained efficiency.
-
We Took Developers out of the Portal: How APIOps and IaC Reshaped Our API Strategy
Dynamic API strategist with expertise in transforming legacy management into efficient APIOps frameworks using Infrastructure as Code (IaC). Proven track record in automating API lifecycles, enhancing security, and fostering developer productivity through CI/CD integration. Adept at driving operational excellence and consistency across environments, enabling rapid deployment and innovation.
-
Zero to Performance Hero: How to Benchmark and Profile Your eBPF Code in Rust
In this article, we will walk through creating a basic eBPF program in Rust. We will intentionally include a performance regression and then use profilers to locate and fix the bug. We will also create benchmarks and track them using a continuous benchmarking tool for CI.
-
Delivering Software Securely: Techniques for Building a Resilient and Secure Code Pipeline
Your CI/CD pipeline can potentially expose sensitive information. Project teams often overlook the importance of securing their pipelines. This article covers approaches and techniques for securing your pipelines.
-
How to Sustain Quality and Velocity in a JavaScript or TypeScript Project?
The JavaScript language and its ever-changing ecosystem of packages and practices can make codebases quickly become hard to maintain. The resulting loss of development velocity and/or code quality can be prevented without rewriting everything from scratch, nor pausing the development of new features. In this article, we have analyzed a few best practices to help avoid that.
-
Thinking Deductively to Understand Complex Software Systems
Thinking differently can allow us to approach problems in new ways. With testing, approaching the problem with a negative approach can lead to more thorough test cases.
-
Effective Test Automation Approaches for Modern CI/CD Pipelines
Shifting left can be used to improve test design and lead to faster, more effective CI/CD pipelines. By focusing on building effective and efficient tests, CI/CD runs can quickly return feedback.
-
Accelerating the Secure Software Delivery Lifecycle with GitOps
Building secure software can be complicated and time-consuming. By employing a GitOps model, security can be safely separated from development, simplifying the delivery process and increasing velocity.
-
Improving CI/CD Pipelines through Observability
CI/CD pipelines are a vital addition to any workflow, but they can be further improved by the selective addition of observability. This article covers what data to monitor, which metrics to track, and how to best visualize the collected data.
-
Why Team-Level Metrics Matter in Software Engineering
In a world where everything can have perspective, context and data, it doesn’t make sense to limit that to just part of your software development process. The DORA metrics can provide insight into the health of your development environment, where value is being delivered and opportunities for improvement. Metrics must be used with careful insight to separate the signal from the noise.
-
Lessons Learned from Enterprise Usage of GitHub Actions
GitHub Actions is an effective CI tool. However, integrating it into enterprise organizations can be challenging. This article looks at best practices for GitHub Actions in the enterprise.
-
Blue-Green Deployment from the Trenches
Introducing blue-green deployments is often a beneficial improvement. However, with some architectures, it can be challenging to make the changes without impeding deployments. This article covers the challenges and lessons learned in implementing blue-green deployments in the real-world.