Operations | Monitoring | ITSM | DevOps | Cloud

The Ingress NGINX project is winding down. For many organizations, this means planning a migration for critical infrastructure. While the HAProxy Kubernetes Ingress Controller is the natural successor for these workloads, a "rip and replace" strategy isn’t always viable. You might have complex configurations, customized annotations, or deployment freezes that make a sudden switch risky. There's a lower-risk path: Place HAProxy in front of your existing Ingress NGINX deployment.

Distributed traces track how your system processed a single request — not what your customers did over time. Confusing the two leads to poorly instrumented systems.

AWS recently experienced a significant outage. The outage took down major services, including parts of McDonald’s mobile ordering system, some Netflix features, and many other applications that relied solely on AWS infrastructure. This event perfectly illustrates why relying on just one cloud platform can be risky.

How we built an AI agent that implements Jira tickets, creates merge requests, and tracks them on its own, and our journey to get to that point.

We’re excited to announce that Speedscale’s proxymock is now available as an OpenClaw skill on ClawHub, bringing powerful API traffic replay capabilities directly into your Claude workflows.

The explosion of AI has created a continuous demand for computing power. At the heart of this need sits one critical resource: GPUs. They have become the hardware of choice for AI and machine learning, particularly deep learning workloads that operate on enormous data sets. However, as organisations race to train larger models and deliver faster inference, many are discovering that owning and operating GPU infrastructure isn’t always practical.

Previously I have written about how useful public cloud storage can be when starting a new project without knowing how much data you will need to store. However, as datasets grow over time, the costs of public cloud storage can become overwhelming. This is where an on premise, or co-located, self-hosted storage system becomes advantageous: it provides the greatest range of benefits, including cost, performance, security, and data sovereignty.