DevOps, Observability, Continuous Delivery, Test in Production, Chaos Engineering, and Software Ownership are all major themes in software development today, but why? In an ideal world, we get everything right the first time, nothing breaks, no one DDOS’ us, and the weather report is “Cloudy With A Chance of Meatballs.” Reality of course is different – and better, to be honest.

Kubernetes clusters can manage large numbers of unrelated workloads concurrently and organizations often choose to deploy projects created by separate teams to shared clusters. Even with relatively light use, the number of deployed objects can quickly become unmanageable, slowing down operational responsiveness and increasing the chance of dangerous mistakes.

There were some big IT headlines this past year. Microsoft acquired GitHub and IBM bought Red Hat. Kubernetes graduated from the CNCF incubator program. And the biggest headline of all—at least to those of us at Datadog, where we live and breathe monitoring—we released Datadog Agent version 6, a completely new monitoring agent written in Go! As we start the new year, we’d like to take a moment to recognize some of the incredible things our engineers accomplished in 2018.

This post is going to be a tad different and longer than what you are used to but I promise, it’s going to be an interesting one. We are going to build a serverless React + GraphQL Web app with Aws amplify and AppSync.

With AWS Lambda, we get scalability and resilience out-of-the-box. What’s more, AWS also provides built-in monitoring, logging and tracing support through CloudWatch and X-Ray. These built-in tools provide a good starting point but many developers eventually outgrow them as their serverless application becomes more complex. In this post, let’s take a serverless application and see how Dashbird can help you debug a serverless application.

The high-level steps for implementing chaos experiments involve: defining your application’s steady state, hypothesizing the steady state in both the control and experimental groups, injecting realistic failures, observing the results, and making changes to your code base/infrastructure as necessary based off of the results.

Continuous Integration and Continuous Delivery (CI/CD) is becoming a standard process in organizations that embrace agile development. CI/CD tools like Bitbucket, Bamboo and Jenkins can help by automating many of the build and deployment steps. However, there are still situations where human intervention is required and Opsgenie can make sure the right responders are notified to take quick action.

Even in this field of work, not everything can be perfected 100%. There are always some situations and cases that will force you to go back or even remain in the present spot, despite your wish to keep going forward at your own pace. In this article, we’ll talk about the cold start impact on latency. What is it? How to fight against it? Is there a successful way of avoiding it or not?