In its Aristotle project, Google tried to define the success of effective teams. The researchers’ main finding was that what really mattered was less about who is on the team, and more about how the team worked together. Most important in teamwork was the presence of psychological safety.

We need to talk.

No, really—one of the hardest parts of wrapping your head around the complexities of CloudNative is getting a handle on all the lingo. Containers, microservices, and orchestration, oh my! When Container Solutions staff meet with clients, we often find that the best place to begin is with a quick Cloud Native 101 to make sure we are all talking about the same things in the same way.

Moving your business to the cloud could mean freeing your organisation from the need to maintain your own antiquated, energy-sucking data centres for everything. Escaping the ever-present threat that a problem in one part of your system could cripple the whole thing. Recruiting—and keeping— smart engineers eager to work with the latest technology.

Getting started with Cloud Native is deceptively easy. Anyone, anywhere—even with zero Cloud Native experience—can simply go online to any public cloud provider, click, and within 10 seconds have a fully-provisioned container running.

In a previous post we covered the history and rules behind capabilities. In this post, we'll go through some examples of how Linux capabilities work and can be used, and the tooling available. We will also take a look at why capabilities are important when working with containers.