DevOps is a culture where full development team works together to complete software development and delivery to production. It is a practice that enables organizations to optimize speed and efficiency across IT functions.

A good DevOps strategy stresses the importance of communication and collaboration between development and operations teams. But these two teams often have conflicting priorities, which can hamper the DevOps experience. Modern chat-based team collaboration tools, such as Microsoft Teams, address this very problem in a simple yet intelligent way. Here are three ways you can use Microsoft Teams to improve your DevOps experience.

Last week, AWS announced a fantastic new feature for AWS CloudFormation, CloudFormation Drift Detection. Drift detection allows you to determine whether the AWS resources controlled by your CloudFormation stacks have drifted from their original configuration. This can happen if you manually adjust properties of your AWS resources. Today, we’re excited to announce a new action to report on your CloudFormation drifted stacks: CloudFormation Stack Drift Report.

We have a running joke at Stackery regarding our tiny little gong that’s used to mark the occasion when we get a new customer. And while I’m all about the sales team celebrating their successes (albeit with a far-too-small gong), I felt like the dev team needed its own way to commemorate major product releases and iterations.

Red Hat OpenShift container platform enables enterprise/start-ups to develop, deploy, and manage existing container applications on-premise or in the cloud. Organizations can make use of proven, efficient, and powerful open-source technologies to create and deploy applications that are secured, scalable, highly available with minimal management and configuration.

I set out to find a credit mechanism or hard-coded limit in packets per second in AWS EC2. After all my findings set out in this series so far, I had one more test to perform around t2.unlimited. I wanted to see how “unlimited” it is and the difference it makes in packet throughput on capable instance types. This post is about my findings.

I hosted a webinar where I covered why logging is important, how to choose a logging provider. And then shared our experience of setting up logging on Kubernetes containers, the Kubernetes logging framework and the logging best practices we’ve implemented internally and supported our customers who run Kubernetes in production.