Operations | Monitoring | ITSM | DevOps | Cloud

We have seen a rapid increase in the development pace of product development in the last few years. As a company, you never stop improving your processes. Successful organizations find different ways to optimize the release process to accelerate their product development cycles. Growing companies, especially those with complex products with many integrations, often struggle to keep pace with the growing complexity of processes.

Privacy enhancing technologies and confidential computing are two of my favorite topics to talk about! So much so that I am writing this blog post on a sunny Saturday afternoon. But wait, what’s that I hear you murmuring? “What is confidential computing? And how does it affect me?” Those are two very good questions.

In computing, virtualization is the creation of a virtual — as opposed to a physical — version of computer hardware platforms, storage devices, and network resources. Virtualization creates virtual resources from physical resources, like hard drives, central processing units (CPUs), and graphic processing units (GPUs). By virtualizing resources, you can combine a network of resources into what appears to users as one object.

Over the past few Boot Camps I’ve done since becoming a Head Nerd, automation has been a continuing topic of discussion, and one that brings up various roadblocks. Many of the MSPs that I have talked to one-to-one after the Boot Camps have said they were “embarrassed” to ask more questions about automating their service delivery as they didn’t want their peers “laughing” at them. If you fall into this category, don’t panic!

Monitoring IT infrastructure and services has always been an essential IT prerequisite. However, your IT monitoring system and security measures need to upgrade with an exponential increase in the number of remote users post-pandemic. For instance, consider this: At the end of a work day, you are notified that one of your critical services has gone down. But the problem is that five teams support different processes of that service.

To many engineers, the idea that you can accurately and comprehensively track your application's user experience using just a few simple metrics might sound far-fetched. Believe it or not, there are four metrics that aim to do just that. They're called the four Golden Signals and should be a core part of your observability and reliability practices.

A microservices catalog is only useful if you are confident that anything stored in it is fully accurate and that the information will not become outdated. How can you be certain that your catalog stays up-to-date in the future? Should you look for an asset in the catalog and, despite finding it there, also double-check GitHub? The service catalog is supposed to be your single source of truth. The purpose is defeated if you have to look for what you need in multiple different places.