Operations | Monitoring | ITSM | DevOps | Cloud

Modern enterprises operate within a digital ecosystem of staggering complexity - spanning on-premises systems, private and public clouds, APIs, containers and SaaS platforms. Business-critical services often rely on a mix of legacy infrastructure and modern applications, each producing huge volumes of metrics, log messages, traces and events.

Kubernetes v1.35 dropped a couple of weeks ago, and while the headlines focus on gang scheduling and in-place resizing going GA, there’s a bigger story here that every platform team needs to understand: Kubernetes is finally acknowledging that cluster utilization is fundamentally broken. At Komodor, we work with hundreds of organizations running Kubernetes at scale.

As AI workloads shift from training to massive-scale inference, SRE teams are about to feel even more pressure. GPU-heavy computing is breaking the assumptions today’s clusters were built on, while enterprises are beginning to trust autonomous operations and cost pressure is pushing consolidation across the cloud-infrastructure stack.

Virtual machines often represent the largest line item in a cloud bill. And for Google Cloud users, the Google Compute Engine (GCE) accounts for a large share of overall spend. GCE offers rich flexibility: you can choose specific machine types, scale up or down instantly, and match compute to load. But understanding how the pricing works is critical before you can unlock full value. On the surface, GCE looks simple. You pay for vCPU, memory, storage, and network.

How about ending this year on a major note? Enter dbForge 2025.3, our new release that covers the entire dbForge product line and brings lots of useful stuff to the table. This includes up-to-date connectivity options, a handful of UI/UX improvements, a wealth of newly supported syntax constructs, and a few more enhancements to make sure you start 2026 with your productivity at an all-time high. Without further ado, let’s take a look!