Operations | Monitoring | ITSM | DevOps | Cloud

Redgate took the main stage earlier today to open PASS Data Community Summit with our keynote, where we shared our vision for the future of the database development experience – one driven by speed, safety, and the intelligent use of AI. As data estates grow in scale and complexity, and as organizations push to deliver software faster than ever, the role of the database is undergoing significant change.

Everyone wants to move faster with AI, but few are truly ready for it. This is where organizations can position themselves better as AI readiness isn’t just about algorithms, it’s about whether your data, systems, and teams are prepared to support intelligent automation safely and effectively.

OpenTelemetry now supports maps, heterogeneous arrays, and byte arrays across all signals. Here’s where these new types shine — and where simple primitives still fit naturally. If you’ve been working with OpenTelemetry for a while, you’re likely familiar with the straightforward key-value approach to attributes. It’s simple, fast, and works well with how most telemetry backends store, index, and query data.

As cloud applications moved from VMs to containers and then to microservices, the amount of background work needed to keep everything running grew just as quickly. You gain speed and flexibility, but you also end up managing clusters, scaling rules, and capacity choices that don’t really add to the product you’re building. AWS Fargate steps in right there. It lets you run your ECS tasks without looking after any servers at all.

Struggling with latency, congestion, or compliance issues? Discover when it’s time to move from public internet to private connectivity. Network operations have never demanded more than they do now, leading many network managers to question whether the public internet is enough. While many organizations begin their network journey with VPNs over the public internet, they often bump into limitations quickly and begin exploring the natural next step – private connectivity.

Engineering leaders face a constant barrage of questions that pull them away from strategic work. A team lead asks about scorecard compliance. A PM wants a status update on a migration. Someone needs incident trend data for a quarterly review. Each question is reasonable. Each requires context switching, digging through dashboards, or pinging someone on your team for a report. What if you could just ask?

If you’ve ever tried to make sense of your AWS bill, you know how fast things get messy. Different accounts, hundreds of services, random tags, and suddenly, no one can say for sure who’s spending what or why the total looks so high. It’s not that teams don’t care about costs — it’s that AWS billing data isn’t always easy to interpret. Finance wants accountability. Engineering wants visibility. And somewhere between the two, ownership disappears.