Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting our team. We will be in touch shortly.Close

  1. Blog
  2. Article

James Nunns
on 12 November 2018

Using Juju to manage evolving complex software


With developers increasingly moving towards microservices – and with the growing prevalence of the cloud as the default platform – software has become more complex than ever.

While installing all of the interconnected applications that make up a modern software stack is becoming easier, the real sting in the tail comes on day two and beyond – when it is time to maintain, upgrade, and scale the deployment.

Deployed software is constantly evolving through updates, configuration changes, changes in scale, and more. Keeping a complex deployment up-to-date and functioning perfectly in spite of these changes represents an immense challenge. And for operators maintaining these deployments, the cost in both time and cognitive load can be tremendous.

The shift to cloud has changed the way people think about operating software. Instead of reasoning about discrete machines, it’s now a matter of carving up compute capability. Juju embraces this mindset by enabling operators to focus on the software model, rather than machines and instance details.

This model-driven approach – made possible through the use of distributed agents – dramatically reduces the complexity of managing complexity. Juju handles upgrades and changes in configuration, scale, and components out of time, removing the complexity of maintaining large estates that can often be time consuming, challenging and costly to manage.

In the past, a stand-alone application was typically enough to solve a particular problem or provide a service to end users. But today’s solutions increasingly demand large bundles of interconnected microservices distributed across many machines, and potentially operating systems, to fulfil a single function.

Whitepaper highlights:

  • How constantly evolving software impacts automation, testing, and onboarding, and how Juju solves these issues
  • How Juju lets operators focus on the software model, rather than machines and instances details
  • How upgrades and changes in configuration, scale and components are handled by Juju

Read the whitepaper

 

Related posts


Serdar Vural
20 September 2024

Canonical and OpenAirInterface to collaborate on open source telecom network infrastructure

5G Article

Canonical is excited to announce that we are collaborating with OpenAirInterface (OAI) to drive the development and promotion of open source software for open radio access networks (Open RAN). Canonical will bring automation in software lifecycle management to OAI’s RAN stack, alongside additional infrastructure capabilities. This will be ...


Michael C. Jaeger
29 April 2024

Kubernetes backups just got easier with the CloudCasa charm from Catalogic

Charms Article

For a native integration for Canonical’s Kubernetes platform, Juju was the perfect fit, and the charm makes consuming CloudCasa seamless for users. ...


Michael C. Jaeger
23 February 2024

What is a Kubernetes operator?

Charms Article

Kubernetes is the open source, industry-standard platform for deploying, managing and scaling containerized applications – and applications on Kubernetes are easier with operators. ...