Operations | Monitoring | ITSM | DevOps | Cloud

We’ve just wrapped up London’s 2025 Open Source Finance Forum (OSFF) in London and in this blog I’ll try to capture the key highlights from this year’s event while they’re still fresh. Dominant themes were the increasing prominence of legislation and governance frameworks, and what these mean for developers and practitioners.

Every engineering team eventually faces this question: “Is our CI/CD setup actually helping us, or is it getting in the way?” The answer isn’t always obvious. CI/CD problems often develop gradually: small issues become accepted workarounds, and those workarounds become standard practice. What once worked well for your team might not fit your current needs or scale. The decision to evaluate new tooling usually builds over time as pain points accumulate and priorities shift.

In recent years, cloud financial management has evolved beyond what many cloud stakeholders anticipated. The overwhelm has led too many companies to struggle to accurately monitor, allocate, and optimize their cloud costs. This issue cost companies about 30% of their cloud budgets in 2022 alone, according to Gartner. With FinOps, you can prevent this bleeding without sacrificing innovation. Yet, taking a manual approach to FinOps can be inefficient and error-prone.

Deploying Helm charts on Kubernetes can be complex, especially when dealing with configuration overrides, security, and environment-specific setups. In this article, we show how Qovery simplifies Helm chart deployment through a seamless developer experience, robust security defaults, and powerful automation, without sacrificing flexibility.

Message queues quietly take care of a lot—buffering workloads, smoothing traffic spikes, and keeping services connected. But they don’t always get much attention until something feels off. Amazon SQS offers a solid set of metrics to help you understand how your queues are doing, whether you’re scaling well or nearing limits. This blog breaks down the key SQS metrics: where to find them, what they mean, and how to respond when things start to shift.

Your Node.js app runs fine on your machine. But inside Docker? You start getting weird crashes—ENOSPC: no space left on device. Chrome headless tests fail out of nowhere. PostgreSQL throws shared memory errors under load. The problem? It’s probably /dev/shm, the shared memory volume Docker sets up by default. Most containers get just 64MB of space here.

A Shopware store goes from smooth to sluggish—pages take 10 seconds to load, even longer in some cases. What happened? In this post, we tell the true story of how one overlooked plugin setting nearly collapsed a storefront, and how it was resolved using native tools. If you’re shipping code in Shopware without clear performance observability, this is your wake-up call. Everything was working, until it wasn’t.

For many enterprises, Drupal has been the backbone of their web operations for years. It’s a battle-tested CMS that handles complex content needs with elegance. But business needs have evolved. Today, it’s rare for a company to rely only on Drupal. They are spinning up Python APIs, .NET backend services, Node.js apps, Java microservices — expanding their digital ecosystems around Drupal’s core.