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.

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?

This is the second of a two-part blog on things to consider when mapping your information architecture. In the first, we shared some tips on how to approach this process based on best practices from the Cortex Customer Engineering team. In this blog, we’ll share how new and existing features in Cortex accelerate creation of a more resilient information architecture.