At Datadog, we operate 40+ Kafka and ZooKeeper clusters that process trillions of datapoints across multiple infrastructure platforms, data centers, and regions every day. Over the course of operating and scaling these clusters to support increasingly diverse and demanding workloads, we’ve learned a lot about Kafka—and what happens when its default behavior doesn’t align with expectations.

Making the move to DevOps can be a daunting undertaking, with many organizations not knowing where to start. I recently had some fun taking a few DevOps assessments to see what solutions are currently in the market. I varied my answers from an organization that fully embraced DevOps to an organization at the beginning of its journey.

Modernizing applications to the cloud will not only save time and resources but also help in scaling your offering! Sounds familiar? Well, it has to since everyone is pacing ahead of the cloud curve. So isn’t it an obvious move for those age-old legacy applications to be modernized to cloud? Here is a quick read on how you can go cloud-native.

It all started with monolith architecture; business logic, user interfaces, and data layers were stored in one big program. As tightly coupled applications, a simple update to the program meant recompiling the entire application and redistributing the program to all users. That led to the difficulty of maintaining consistent program versions and distribution across all clients in order to ensure stability and alignment. This made the monolith approach inefficient and cumbersome.

From workload shifts to deployment models, Spiceworks examines emerging public cloud trends in businesses across North America and Europe. In recent years, cloud computing technology has changed the way many companies handle IT. Using the public cloud computing model, IT departments have the option to pay-as-they-go while rapidly spinning up services, applications, or instances in a cloud provider’s data center, scaling them up and down as demand changes.

Pune, India – June 21, 2019 – CloudHedge Technologies today announced it raised funding from NTT DATA Corporation, Japan. CloudHedge’s technology agnostic platform brings automation and intelligence to enterprises in their digital journey to modernize applications. In addition, CloudHedge has grown multi-fold in containers, Kubernetes and cloud ecosystems around the globe.

StackStorm can’t pour you a beer. But now it can keep track of who owes you a beer! Read on for more info about the new beertab pack, and other new packs & interesting StackStorm Exchange updates.

While there are some very good sources out there on how to manage a critical incident, Google also wrote a chapter on incident management in their book, “Site Reliability Engineering”. In this chapter, the folks at Google present their approach to a well-designed critical incident management process.

In the 20th century we were programmers. In the 21st century, developers. With the massification of telecommunications worldwide, operators began to help us in our work. That’s where the term DevOps (“developers” and “operations”) arose, which implies the concept of collaboration of both teams. But since change is the only constant, other practical considerations have forced us to see the entire forest instead of just a few trees.

I was recently called upon to secure an Nginx web server with HTTPS, and my goal was to set this up with a certificate obtained from AWS Certificate Manager. It took me a while to figure out how to get everything configured and working. Hopefully someone else who is attempting to do the same thing will read this and I can save you some time!