A passing test in a monolith traditionally offered a relatively straightforward signal. The code behaved as expected under the conditions tested. The function produced the expected output. The integration with the database worked. The deployment was probably safe within those limits. A passing test in a cloud-native system can offer
SUSE this week at the KubeCon + CloudNativeCon North America 2026 conference made a bevy of updates to its tools and frameworks for managing Kubernetes clusters, including a set of specialized artificial intelligence (AI) agents that are invoked via a natural language AI assistant dubbed Liz that the company added
Cloud-native fraud detection misses coordinated attacks when services operate in isolation. Learn how cross-service correlation exposes fraud without compromising privacy.
Cloud-native infrastructure has changed the way organizations think about resilience. Kubernetes can restart failed containers, replace pods, schedule workloads on healthy nodes and help applications recover from failures that once required manual intervention. That is real progress. But there is a difference between keeping workloads running and keeping infrastructure recoverable.
Amazon Web Services (AWS) today added an emulation capability that makes it simpler for application developers to build applications on a local machine before deploying them in the cloud. Tom “Spot” Callaway, principal open source software strategist for AWS, said the open source AWS Emulator project makes it possible to build and test applications on […] [...]
ControlTheory today at the KubeCon + CloudNativeCon North America 2026 conference added support for metrics and traces to a platform that analyzes telemetry data at the point where it is collected. Company CEO Bob Quillin said version 2.0 of the Dstl8 platform is now able to analyze logs, traces and metrics in a way that […] [...]
Modern systems fail in ways that dashboards were never designed to explain. A single checkout failure can trace back to a Kubernetes node under memory pressure, a slow third-party API, or a log line nobody was watching. Teams now run hundreds of services, thousands of containers and millions of telemetry events per minute. Humans can […] [...]
