Operations | Monitoring | ITSM | DevOps | Cloud

This article is a part of our DevOps blog series inspired by our DevOps bootcamp live streams available to watch on our YouTube channel. As a developer constantly working with code, it’s only natural to feel the need to test your code frequently. Testing helps detect bugs and protect against any of the same in the future.

Recently we had the privilege of being named a Gartner Cool Vendor in the Monitoring and Observability category. The funny thing is, while this is definitely the closest Gartner category for our solution, we aren’t really used to thinking about Komodor as a monitoring and observability tool.

Calico Cloud has just celebrated its 1-year anniversary! And what better way to celebrate than to launch new features and capabilities that help users address their most urgent cloud security needs. Over the past year, the Tigera team has seen rapid adoption of Calico Cloud for security and observability of cloud-native applications.

When business is growing rapidly, the necessity to scale the processes is obvious. If your initial infrastructure hasn’t been thought through with scalability in mind, growing your infrastructure may be quite painful. The common tactic, in this case, is to transition to cloud native architecture. In this post, we will talk about what you need to know when you’re scaling up with the cloud so that you can weigh the pros and cons and make an informed decision.

We covered the what, when and why of Service Mesh in a previous post. Now I’d like to talk about why they are critical in Kubernetes. To understand the importance of using service meshes when working with microservices-based applications, let’s start with a story. Suppose that you are working on a big microservices-based banking application, where any mistake can have serious impacts. One day the development team receives a feature request to add a rating functionality to the application.