The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Welcome to the second edition of Serverless from the Trenches, our series of bite-sized blog posts aimed at developers and DevOps working in serverless. Each article will focus on a different technique or tool to solve a real-world problem and – hopefully – help make your work in serverless more productive. This week we look at how to add Cognito to your integration tests flow, making for true black box testing.
We’ve all read those op-eds in the Smarter Living section of NYT about impostors syndrome. After all, they have been getting more and more traction as a new generation enters the associate-level in their career.
Canary releases are a powerful technique for updating large-scale production environments safely. The idea is simple: deploy the update to a subset of your environment, pause and monitor to ensure everything is healthy, and then deploy to the next subset. But implementing these staged releases can be challenging, as you’ll need to retool your deployment pipeline and build programmatic health checks to validate the success of each canary release.
Last month, members of the Datadog community convened in Seattle for our customer summit. There, they discussed new developments in monitoring dynamic infrastructure and applications, learned about the latest updates to the Datadog platform, and shared tips, tools, and techniques from their own experiences.
The early adopters have begun to find a great degree of success and it is now time for the more mainstream enterprise to get off the proverbial wall and begin exploring containers and other areas of the cloud-native landscape. However, there is a need to mitigate or manage the risk of adopting new technology as it does introduce a dimension of change that accompanies any transformation.
Everybody climb aboard the hype train with me. Today, we’re going to study a new job title: the DevOps engineer. This role is getting popular in the same way that the full-stack developer role became popular before it. In fact, one could argue that the DevOps engineer is an extension of the full-stack developer in that both seek to extend our ownership of our software.
