Kubernetes (k8s) adoption has skyrocketed since its 2014 introduction, becoming one of the most popular open source container orchestration platforms for its power and flexibility. K8s reduce costs by improving efficiency, optimizing resource use, and eliminating redundancies. But cost savings in Kubernetes can be tricky to maintain. In fact, a 2021 survey of 178 organizations showed that costs associated with k8s can actually increase from insufficient monitoring, resulting in overspend.

The first fifteen minutes of an incident set the tone for the rest of the resolution process. But what makes the difference between a rapid response and a stressful scramble—clear ownership—hasn't always been easy to ascertain. In this article, we’ll cover how Cortex, an internal developer portal, can be your team’s source of truth to accelerate the incident management process, and reduce MTTR.

We've upgraded the Team catalog experience with the same level of dimensionality as the Services, Resources, and Domains Catalogs. Now users can add more information about teams like relevant custom data, links, and integrations, and drill down into aggregate team activities and performance.

As organizations increasingly adopt serverless architectures and embrace the benefits of microservices, managing logs in this dynamic environment presents unique challenges. In this blog, we’re taking a closer look at the differences between serverless and traditional log management, as well as 8 challenges associated with log management for serverless microservices.

Updating a software version, moving to Kubernetes, onboarding a new CI/CD tool... some of these decisions could have enormous productivity upside for your team, while others carry significant risk if not executed by a certain deadline. In either event, getting everyone aligned with what to do, when—is never an easy task. Learn what to avoid for speedy migrations, and how Cortex helps.

This is the second blog in our deep dive series on serverless architectures. In the first installment, we explored the benefits and trade-offs of microservices and serverless architectures, highlighting the case of Amazon Prime Video's architectural redesign for cost optimization.

Working on software infrastructure for the sake of infrastructure is rarely a good use of time. That probably sounds obvious, but perhaps the next question is less straightforward: what should engineering platform teams do instead?

If you are a SaaS provider making an application that deals with, say, a health registry or some personal information of the public, you realize how crucial it is to maintain their confidentiality. It is these situations that demand a previous encryption of data followed by a prompt tracing mechanism that finds out the faults right at the moment or prior to its occurrence. And what better way to keep track of your application than tracing?

In microservices architectures, apps are broken down into small, independent services that communicate with each other using APIs in a synchronous or asynchronous way.