Atomist release drift management feature for cloud native software

Cloud native company, Atomist, has announced its new Drift Management feature. This will be a component of its software delivery automation platform that provides users with a code consistency engine and visual reporting.

Its hoped that the feature, which is now in beta, will bring enterprise and DevOps teams the information they need to ship faster as well as improving both security and quality.

Atomist says that with an automated way of achieving cohesion in the quality of their codebases, employees will now have a single tool to expose, manage and fix drift in their code.

“Organizations are under pressure to work faster and be more agile, yet legacy delivery tools aren’t designed for today’s containerized microservices environments,” said Rod Johnson, CEO and co-founder of Atomist. “Our goal is to enable teams to take back control of their cloud native development. With the addition of Drift Management, Atomist is the essential platform to comprehend your software landscape, drive your team towards convergence on best practices and achieve consistency across all delivery policies.”

A developer-friendly approach to drift management

Because firms need a reliable way to recognise and manage drift issues, Atomist has purposely built the newest feature with a developer-friendly approach. It hopes this will let teams visualise the usage of tech quickly and identify drift alongside any other issues that may occur.

It also aims to set policies that address issues as well as tracking and monitoring progress towards policy goals.

Main characters of the product

A core element of the drift management feature is an open source project that analyses repositories for drift. Another component is that the drift report aspect provides a visual representation of what’s happening within the codebase of an organisation. Complexities are then internalised, and vulnerabilities dealt with quickly.

Lastly, the policy manager captures and tracks changes and variations in code.

Why the product is needed

Talking to DevOps Online about why the company wanted to design the new feature. Johnson spoke of how the firm noticed the gaps in tooling and wanted to make a difference to this.

Johnson says: “[Before], organisations had a very small number of very large applications. These days they have a very large number of relatively small applications…. Today there is a gap in tooling. We are now building a platform to comprehend these projects, help to get them towards best practice and to make them more consistent.”

He continued that the feature “gives you the ability to react to important changes in your code and configuration.”

Customer focused

Ryan Day, Co-Founder and COO at Atomist also spoke to DevOps Online about the building of the new product. He says, “This announcement around drift management, a lot of it was driven by our customers and there is a need specifically around driving consistency that we are putting at the top of our platform. “

Day added more about the reasoning behind making the tool. He continues: “It’s really geared at the idea that this isn’t about dependencies. What if you harvested ports exposed in an application and that manifests inside of a DR file? What if there are secrets inside of Kubernetes configuration that shouldn’t be there? We are effectively an engine to spot, recognise and remediate these kinds of patterns. In a world where everything is code, it sort of sits as a repository. It sits at a ground zero where people can take action.”