Operations | Monitoring | ITSM | DevOps | Cloud

Continuous integration is a DevOps practice, where developers continuously integrate the code changes into a central repository. It most often refers to the build or the integration stage of the software release process. A continuous integration service helps to automatically build and run unit tests on the new code changes to find any errors instantly.

Most Series A and B companies are born in the cloud. Instead of the traditional mainframe architecture, they use AWS, Kubernetes and the likes to run their production environments. While striving to do things faster and better, we must address the other side of the coin: How do you support the constant shifts inherent in these environments? Chaos engineering allows you to observe your environment continuously and reliably.

Starting with version 16.8, React provides a way to use component and global state without the need for class components. This does not mean that Hooks are a replacement for class components, though. There are some benefits of using class components, which I will describe later in this tutorial.

Axios is a promise-based HTTP library that lets developers make requests to either their own or a third-party server to fetch data. It offers different ways of making requests such as GET, POST, PUT/PATCH, and DELETE. In this tutorial, I will explain how Axios interacts with applications, describe the structure of Axios requests and responses, how to make requests to an API, and how to write tests for your requests using CircleCI.

We are excited to announce that PagerDuty® Runbook Automation and PagerDuty® Process Automation On Prem are now available on the AWS Marketplace, the leading global cloud provider. With more than 200 different cloud services, AWS makes it simple and attractive to build and grow your cloud-native business and/or migrate your existing infrastructure to the cloud, so you can begin to take advantage of the unlimited scale, agility, and flexibility the cloud offers.

Our last Qovery Demo Day took place on a live on the first Thursday of May. This event aims to give you some insights into what we did during the past month and what’s next and showcase some of our new features. During this demo day, Bilel (Software Engineer at Qovery) and Romain (Software Engineer at Qovery) joined me to talk about Terraform Improvements demo and Docker Build Improvements demo.

Most organizations that make software — from small startups to multi-billion-dollar behemoths — use third-party libraries and tools to develop their applications. Modern apps depend on many external components to build and deliver software to customers. These libraries and tools are collectively called the software supply chain. A software supply chain for a typical web app may include components like these.

Bitbucket Cloud is making changes to pull request diff functionality that will improve diff performance, particularly on complex diffs. We are changing our diff algorithm from what we call a '3-way' diff to a 2-way 'three-dot' diff, which will show the difference between the tip of a source branch and the commit from which it branched off the destination, as shown below. This new diff will be implemented on the Pull request page and Branch page in the coming weeks.

This post is the second in a series of deeper dive articles on the four DORA metrics. The first metric we looked at was Deployment Frequency, which is about how often code can get released to end users. In this second article, we’ll look at Change Lead Time, arguably the metric most familiar to developers.