Systems | Development | Analytics | API | Testing

Author: Adam Wolf ClearML Enterprise v3.28 offers new features and improvements to help administrators monitor usage, enforce policies, and streamline operations across large, multi-team environments. This release introduces enhanced usage metering with a simplified interface, improved resource policy management, improved dataset controls, and UI enhancements to provide greater clarity, control, and productivity for AI teams.

Having a build cache solution is a powerful way to speed up builds, especially at scale. Bitrise Build Cache already accelerates builds across multiple ecosystems, but to get the most out of it we also need to optimize the build cache clients themselves and ensure stability across changing network environments. In this blog post, I’ll walk through the steps we took to improve stability and performance for Bitrise Build Cache customers.

If you're running Node.js in production, you've likely heard the buzz around OpenTelemetry. It's the industry standard for observability, backed by major vendors, and it promises vendor-neutral telemetry collection across your entire stack. For many teams, it's a game-changer: finally, a unified way to collect traces, metrics, and logs without getting locked into a single vendor's ecosystem.

The promise of agentic AI is clear: autonomous systems that can reason, plan, and act on your behalf. But there's a fundamental problem standing between that vision and enterprise reality: agents need context to make decisions, and that context lives scattered across your organization. Context is any data — or any abstraction that enables access to data — that an agent needs to do its job. Customer records in your CRM. Inventory levels behind your fulfillment APIs.

Kong Operator 2.1 is a significant update for our customers, opening up integration into the Kong ecosystem for our Kubernetes customers. With Kong Ingress Controller, when your Control Plane was hosted in Kong Konnect, and you were using Kubernetes Gateway API, your dataplane, routes, and services were in read-only mode.

I’ve worked with Apache Kafka since 2019, and deciding how to design and implement client failover was a sticking point in almost every use case I dealt with. Even for Confluent customers—who have the benefit of features such as Confluent Replicator, Multi-Region Clusters, and Cluster Linking—ensuring seamless failover between Kafka environments is a challenging problem.