Operations | Monitoring | ITSM | DevOps | Cloud

Open source software, as the name suggests, is developed in the open. The software can be freely inspected by anyone, and can be freely patched as required to suit the security requirements of the organisation running it. Any publicly identified security issues are centrally triaged and tracked.

In the first post of this series, we covered the general idea and benefits of model-driven observability with Juju. In the second post, we dived into the Juju topology and its benefits with respect to entity stability and metrics continuity. In this post, we discuss how the Juju topology enables grouping and management of alerts, helps prevent alert storms, and how that relates with SRE practices.

Many organizations are shifting vast portions of their applications and infrastructure to the cloud in pursuit of lower IT costs, greater business agility, improved security, and accelerated corporate growth.

If your organization is frustrated with how long it takes to roll out new applications and updates, they are not alone. Speed-to-market is an obsession at many companies today (see call-out box below), so anything that restricts or slows it down is a problem.

This tutorial is a follow-up to TurboCharging your Android Gradle builds using build cache . The key focus of this post is the remote build cache, a build speed acceleration technology that can be implemented for both local and CI builds. This is a technology worth knowing about because: Gradle provides a build cache node available as a Docker image. You can host this image in a number of ways.