Originally published on CD Foundation. This was my first contribution to a collaborative CD Foundation blog post. A lot of interesting insights from a very smart group of people. Worth checking out. “Building and releasing software is complex. Teams want to build software faster. Organizations want to get their products in front of users as soon as possible. To stay competitive, companies invest in automation. To that end, many of them started moving their pipelines to some form of CI/CD....

Originally published on Cprime. The Cloud Native Computing Foundation (CNCF) defines Cloud Native as “technologies [that] empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach”. Cloud native is a modern approach to building, running, and managing services. Cloud native systems aim to achieve rapid change, large scale, and reliability....

Originally published on Cprime. Assessing your system’s reliability through SLOs is a great way to really understand and measure how happy users are with your service(s). Error Budgets give you the amount of reliability you have left before users are unhappy. Ideally, you want to be alerted way before users are dissatisfied and take the appropriate measures to ensure they aren’t. How can you achieve that? That’s where alerting on SLOs and Error Budget Policies come into the picture....

“A service mesh is a dedicated infrastructure layer that decouples some of the critical operational tasks of a distributed application from its business logic. Large-scale, Kubernetes-hosted microservice applications are natural candidates for service meshes due to their complex requirements of inter-services communication (e.g., retries, timeouts, traffic splitting), observability (e.g., metrics, logs, traces), and security features (e.g., authentication, authorization, encryption). Service meshes can offload many operational concerns of the Kubernetes cluster, leaving the developers to focus on business logic....

Originally published on Squadcast. Observability is the practice of assessing a system’s internal state by observing its external outputs. Through instrumentation, systems can provide telemetry such as metrics, traces, and logs that help organizations better understand, debug, maintain and evolve their platforms. SREs use many tools and practices to manage services at scale and observability is a crucial part of it. Observability enhances SRE by allowing its practitioners to infer a system’s internal state....