Netdata is made up from agile teams who are deeply committed to improving the usability of our product. We want to respond to our users and introduce in-demand features. Working directly with our community is the best way to make Netdata better. But we face the same the dilemma as all agile teams: How do we do this safely?

Developing for Google Cloud Run in a hybrid system managed by Anthos isn’t a solo race, it’s a relay between cloud and on-prem. To win, you’ll need an advanced Docker registry that can swiftly pass your containers for Cloud Run functions from one environment to the next. In our example hybrid architecture, you’ll see how JFrog Container Registry can be that reliable relay partner.

This guide will give you key strategies for deploying the same application on multiple AWS accounts. If you have multiple AWS accounts running, multi-account deployments make often make sense. If your developers have created an application within their dev environment (which has its own AWS Account), they’ll naturally want to move it over to production (with a separate AWS Account).

Azure Event Grid facilitates building event-driven serverless apps that can effectively solve a real-time business problems with a focus on the core logic rather than the infrastructure. Event Grid is designed for high availability, consistent performance, and dynamic scale. Event Grid can simplify event-based apps, as this serves as a single service to manage routing of all events from any source to any destination. Before we proceed further, it is important to understand what an ‘event’ is.

The power of community, and doing things together as that community, was the overarching theme in much of KubeCon/CloudnativeCon presentations. We were incredibly lucky to be able to attend, experience and learn from so many Cloud Native experts and developers over the past week.

With the growing complexity and velocity of security threats in dynamic, cloud-native environments, it’s more important than ever for security teams to have the same visibility into their infrastructure, network, and applications that developers and operations do. Conversely, as developers and operations become responsible for securing their services, they need their monitoring platform to help surface possible threats.

It is increasingly clear that tools developed to keep a single system or a small cluster running are no longer sufficient in today’s highly distributed, complex environment. The tools that offer service assurance must be able to move their way through complex application systems and prevent slowdowns or application failures. These complex systems now include physical systems, virtual systems and even systems found in a cloud service provider’s data center.