One of the most impressive books on DevOps, “The DevOps Handbook”, emphasis three fundamental principles underpinning DevOps: systems thinking, amplify feedback loops, and continual experimentation & learning. Amplifying feedback loops is described as creating the right to left feedback loops, which helps corrections to be made continually, by Gene Kim in his blog post. But, let’s start with why we should do this in the first place.

DevOps teams use a number of monitoring, project management, log management, and other IT management tools to receive alerts when something’s up. While this helps IT teams keep their system up and running at all times, the content of the alerts sent by some applications might not be relevant or insightful to the technicians who work on those issues. Now, with the Alarm Modifier feature, you can add new fields to an alarm, modify existing fields, rename fields, or remove them altogether.

Deployment errors can be expensive mistakes. Successful development teams understand that their deployment tools must help structure and organize updates in a systematic and safe way. Regardless of your team’s preferred programming language, these tools can help. Discover the best tools for deployment.

Bitbucket Server is the convergence of individual work and team collaboration. Administrators ensure the git server availability, enabling developers to complete deployment cycles. Those teams operate independently but share common goals like, automating and simplifying repetitive tasks.

How I used Swarm to rearchitect a monolith. Some decisions take time to make. Should I learn Golang or Elixir? Should I use Docker Swarm or Kubernetes? You start by learning Docker, then you outgrow it when you want to deploy an app on more than one server. But you must choose between Swarm and k8s…

Throughout this series we have been exploring how to use serverless architectures to our advantage. In this article I will show you: How to create a serverless slack command using Node.js & Up, Best Practices when developing serverless applications, A curated list of serverless resources.

In Part 2: Serverless Scales I briefly touched on how a serverless architecture can have a cost benefit. In this post, I will go over: How to approach and analyze the cost of serverless, Two detailed examples of a cost analysis.

In Part 1: What is Serverless? I talked about how one of the biggest pros to a serverless architecture is how well it scales and how high availability is baked in. In this post I’ll go over: How a traditional highly available scalable architecture works, How a scalable serverless architecture works, How you can benefit from a serverless architecture.

In this post we’ll answer the following questions: What is serverless architecture? (and what it’s not), What are the pros & cons of serverless?

This article strives to keep things as simple as possible using backwards-compatible freestyle jobs. The idea is to use the power and simplicity of Git rather than introduce complexity from - and coupling to - Jenkins. Get tips to refine the continuous delivery pipeline process with Git and Jenkins to make life easier.