Operations | Monitoring | ITSM | DevOps | Cloud

In a previous article, we talked about how you could use BAM to do advanced management of dead lettered messages on the Azure Service Bus using a scenario like below. This article will show how you can set up this kind of example. Let’s assume your Order Processing functions are already in place, and your starting point is that sometimes you will get dead-lettered messages, and we need to implement the Send message to the BAM logic app and configure Serverless360.

Before you can answer this question, I like to step back and take a good look at the history of computing. Mainframes and legacy client-server applications were monolithic—all the processing took place on a single set of hardware. As hardware grew cheaper, and especially after widespread hardware virtualization came to fruition, these trends gave way to the widespread development of distributed systems. I began to see this trend during my time as an architect at a large cable and telecom provider.

There is a lot of the art of the possible between the GitOps Engine, Argo CD, and the Application-as-Code platform, Shipa. In a recent blog post, we outlined the power of a one-line developer experience. Though if you are unfamiliar with ArgoCD, here is a guide to get you started with Argo CD and leveraging Shipa for your first deployment.

In my prior blog, Continuous Service Virtualization, Part 1: Introduction and Best Practices, we offered an introduction to continuous service virtualization (SV) and discussed some key best practices. In this, the second and final post in the series, we will discuss the continuous SV lifecycle and how it helps to optimize DevOps and the continuous integration/continuous delivery (CI/CD) pipeline.

Service virtualization (SV) has evolved as a popular technique and technology over the last decade. Traditionally, SV has primarily been used by testers to simulate other application components that the application under test interacts with. Typically, virtual services have been created and maintained by center of excellence (COE) teams.

Not all cloud cost management tools are equal. Whether you’re in the process of evaluating cloud cost management vendors or already have a tool in place, here are 19 questions you should ask to ensure you have all the capabilities needed to maximize performance and minimize cost of your hybrid cloud deployment across the following.

With rising awareness and increasing calls for action, the pressure is on to improve your organization’s energy sustainability. While frequently overlooked, moving your IT workloads to the cloud is one of the quickest ways to achieve a material reduction in your carbon footprint. Organizations typically look to the cloud to improve agility, scalability, and reduce costs.

I recently started working at SUSE. Before joining SUSE, my Kubernetes experience included vanilla Kubernetes, AKS and EKS but mostly OpenShift and Red Hat Advanced Cluster Management. I worked in technical pre-sales, so I knew about Rancher, K3s and RKE and their key features but I never spent time with them. When I joined SUSE, I started testing Rancher, Rancher Desktop, K3s, k3d and RKE2 and I had a great time with them. First things first, I will

When someone says a website is available, they mean that they can access that website. The application they’re trying to reach is up and working properly. High availability means that the website is up most of the time throughout the year. Companies can even put a percentage on this, striving for 100% availability, but typically getting somewhere a bit less, such as 99.9% or 99.99%.

For some developers, SemVer can look just cosmetic, nice to have, or simply useless. But SemVer format is mandatory to make reliable software. I'll explain how over one year, we encountered 2 issues related to SemVer. The first one was critical and led to a production outage, while the other was a lot of trouble for several companies to upgrade a managed service.