Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes and Docker each play a vital role in modern, microservices-based application development. Since Kubernetes and Docker work in unison to help develop, deploy, and manage large-scale applications – they are not mutually exclusive technologies and they are certainly not in competition with each other. Nevertheless, Kubernetes and Docker are often misunderstood by the non-developer community. To clear up the confusion around Kubernetes vs. Docker, we’ve written this guide.

Since the release of Sensu Go, many in our community have told us Sensu is easier and faster to deploy, more portable, and more compatible with containerized and ephemeral environments (as compared to Sensu Core, the original version of Sensu). In a recent webinar, I talked about integrating Sensu Go with your CI/CD pipeline and how to use the sensuctl prune command to keep your Sensu resources in a declarative state, reducing dependence on traditional configuration management tools.

ROS, the Robot Operating System, is the platform of choice for robot development. However, the breadth and depth of existing documentation can be daunting for the ROS beginner. Where should you start learning about ROS 2 on Ubuntu? All robots based on ROS and ROS 2 are programmed using five simple but core constructs: In this tutorial and associated video we’ll introduce these concepts with simulated robots.

“Kubernetes vs. Docker” is a phrase that you hear more and more these days as Kubernetes becomes ever more popular as a container orchestration solution. However, “Kubernetes vs. Docker” is also a somewhat misleading phrase. When you break it down, these words don’t mean what many people intend them to mean, because Docker and Kubernetes aren’t direct competitors.

DevOpsDays Chicago 2020 was held on September 1, online. It was the first time the conference was held virtually due to the coronavirus pandemic. I was excited to attend for a couple of reasons. First, DevOpsDays Chicago is one of the better known and respected DevOpsDays held in the US. I’d never been able to attend it before, so it was great to get the opportunity. Also, I’d been missing the DevOpsDays community.

Almost everyone knows that working with third-party APIs can be challenging. Sometimes the errors happen unexpectedly. Sometimes the error information that you receive is inaccurate. While most people feel these pains acutely, I’d like to share how we answer these challenges at FireHydrant and how it’s helped us avoid headaches and stress.

Your app is done and the client is ready to launch! Everything looks great. But how can you ensure that you will achieve your SLA for uptime? How are you tracking revenue growth (& optimizing)? Do you know how many users you have, and what they’re doing at any given moment in the app? What you need is a monitoring platform that will be able to track these different types of data in one place.