Operations | Monitoring | ITSM | DevOps | Cloud

First, I’d like to say how happy and lucky I feel to be working at Redgate on Flyway. I’m one of two Senior Product Managers in Flyway and we’ve been looking for a third to join us. We work alongside the Flyway Group Leadership Team (Group Product Manager, Architect, Lead Designer, and Development Manager) and four amazing engineering teams with embedded designers. We also work with the Product Support, Marketing, Sales, and Customer Success teams.

Teams work on databases across multiple environments (e.g., Development, Test, QA/UAT, Production) and differences can happen in these databases over time. A hot fix applied directly to Production or a quick change applied in Test while troubleshooting are examples of how the schema can diverge from what’s expected. These differences are known as drift and can cause problems with deployments making them unpredictable and harder to troubleshoot.

Managing assets across multiple business locations has become significantly more complex in recent years. As enterprises expand geographically, often operating across 10, 20, or even 50+ locations, the challenge of maintaining visibility, control, and accountability over assets increases exponentially. In 2026, asset tracking is no longer a “nice to have” capability for distributed enterprises; it is a foundational requirement for operational efficiency, compliance, and cost control.

2025 has been quite a year! As we enter into 2026, we want to share all the great features that VictoriaMetrics Cloud has brought in the last quarter. Remember that this Quarterly Live Update is available in video format as well here: Let’s get to it!

Automation revealed truth. AI learned to reason from it. Now, systems are beginning to understand themselves. The self-aware enterprise isn’t a vision of autonomy. It’s a model of awareness. It sees, understands, and acts with precision based on verified knowledge of how it operates. This is the next evolution of intelligence in IT. Not artificial. Not imagined. Built.

The IT landscape has evolved rapidly, transitioning from monolithic applications to complex, distributed system architectures comprising microservices that run on platforms like Kubernetes. With this added complexity, simply checking if a server is running is no longer sufficient. As IT professionals, we need insight into what’s really happening inside these systems. That’s where observability comes in.

Kubernetes v1.35 marks an important turning point for cluster networking. The IPVS backend for kube-proxy has been officially deprecated, and future Kubernetes releases will remove it entirely. If your clusters still rely on IPVS, the clock is now very much ticking. Staying on IPVS is not just a matter of running older technology. As upstream support winds down, IPVS receives less testing, fewer fixes, and less attention overall.

Is the "Heroku Tax" draining your budget? Compare Heroku vs. Kubernetes in 2026. Learn how to solve complex orchestration challenges, like queue-based autoscaling and microservice sprawl, without the DevOps toil.

Is the EKS operational burden outweighing its benefits? Learn how to migrate from EKS to ECS, the technical trade-offs of AWS-native orchestration, and how to get ECS-level simplicity without losing Kubernetes power.

More than half of all connections to web services now originate from mobile devices. Mobile apps are no longer peripheral - they are central to how businesses engage customers, deliver services, and generate revenue. Despite this shift, many organizations still rely on observability tools that are fundamentally server-centric. These platforms are adept at monitoring backend health, but they often fail to capture what’s happening at the edge - on the mobile device itself.