[Feedback please] Wecloming new users to Juju

Hi all, I’ve taken up the baton of improving prospective users’ first impressions of the project and Juju’s onboarding experience overall.

After a few iterations, I am interested in gathering feedback. What resonates? What would you be most happy to point people to?

Version 1:

Juju is the simplest way to manage software that spans machines.

Juju allows you to retain a high-level understanding of all the parts of your system without being bogged down needing to know every hostname, every machine, every subnet and every specification of every storage volume.

Focus on your applications and their relations. Create a development environment on your laptop, then recreate that environment on the public cloud, onto bare metal servers or into a Kubernetes cluster.

Maximise your productivity by encapsulating specialist knowledge into Juju charms. They create repeatable, systematic and secure devops practices for all stages of your product’s lifecycle. Juju simplifies deployment, maintenance, scaling up and winding down.

Another attempt:

Why Juju?

  • Reduce complexity
  • Enable repeatability
  • Codify operations knowledge
  • Simplify day two
  • Maintain portability

If your infrastructure can’t be understood by everyone in your organisation, there’s an issue. Juju focuses on the applications that your deployment defines and how they are related.

Requiring everyone to know every hostname, every machine, every subnet and every storage volume is brittle. This means change is complicated, on-boarding is difficult and tends to create knowledge silos. Juju makes those details available, but places the deployment model at the front.

With Juju, your team maintains a practical high-level view that makes your backend more adaptable to changes over time. Extending your product should be as simple as deploying its first prototype.

What is Juju?

Juju is a devops tool that reduces operational complexity through application modelling. Once a model is described, Juju identifies the necessary steps to make that model a reality.

Juju has three core concepts: models, applications and relations. Consider a whiteboard drawing of your service. The whiteboard’s border is the model, its circles are applications and the lines between the circles are relations.

Juju uses an active agent deployed alongside your applications. That agent orchestrates infrastructure, and manages applications through the product life cycle.

1 Like

This is probably a little late by now, but I like the second one more. :slight_smile:

Me too :slight_smile:

The readme ultimately got changed to:

Simple, secure and stable devops tooling. Juju keeps complexity low and productivity high. Built to manage today’s complex application architectures wherever they are run.

Built for

  • SRE and operations teams
  • Developers
  • Data engineers

Excels at

  • Making your deployment understandable
  • Simplifying post-install operations, such as upgrades, updates and configuration management
  • Managing hybrid-cloud services, whether on Kubernetes, VMs, bare metal or any combination

Why Juju?

Juju increases your productivity and decreases your costs.

  • Increase confidence
    If you have ever put off upgrading something in production because something might break, then consider Juju. Juju allows applications to automatically negotiate their configuration, creating optimal settings dynamically.

  • Reduce complexity
    Microservices have made applications simpler, but operations more complex. Regain your understanding of the whole stack.

  • Strengthen operations knowledge
    Everyone has their in-house expert. Encapsulating their know-how in charms distributes that knowledge throughout the business.

  • Simplify day two and beyond
    Upgrades, provisioning new capacity, applying configuration changes can be subtle and difficult. Juju takes responsibility for them, as well as deployment.

  • Maintain portability and repeatability
    Retain control over your deployment and eliminate the need for vendor-specific offerings. Your devops tooling should be cloud-agnostic and Kubernetes-aware.