Why Observability Was Key to Citigroup’s Cloud Native Transition

Article for Chronosphere by Eric Newcomer

Going cloud native requires the right tools, especially modern observability, a new developer culture and engineering best practices.

You know that you want to move your applications to the cloud to achieve the always-on, scalable, responsive and agile capabilities your customers expect. But you also know that your developers may not be ready for the challenges in designing, developing, deploying and operating microservices-based applications. You want to be sure your developers have the support they need to be productive. You want them to spend their time realizing the benefits of cloud native computing, not chasing issues and resolving problems.

Microservices, containers and DevOps have given organizations the power to scale and adapt and give organizations the agility they need to be competitive. But these technologies and techniques tend to increase complexity, challenges that manifest through unprecedented volumes of observability data and unpredictable and rapidly increasing observability costs.

Many enterprise developers are not familiar with cloud native observability technologies or with the best practices for using them to achieve the benefits of cloud native infrastructure. Dealing with cloud native complexity places a new burden on developers who are responsible for achieving scalability, reliability and agility. They need a concise, focused dashboard to be as productive as possible.

Click here to read the entire article.

SHARE THIS: