While Cloud Computing continues to revolutionize the IT industry, DevOps supercharged the pace of this transformation over the last few years. Companies strive to achieve a competitive advantage by both improving efficiency and cutting costs, with Cloud-based technical infrastructures being a big part of this equation. Increasingly these firms use Fugue, an automated tool to assist in the governance of Cloud operations.
Let’s take a high level overview of Fugue and its functionality to see if it makes sense as part of your organization’s Cloud investment. If you are looking at turning DevOps into DevSecOps, it might be the perfect fit.
What is Fugue?
At its heart, Fugue provides automated services for regulatory compliance and corporate policies as they relate to a Cloud infrastructure. It uses a code-based model to facilitate this infrastructure management, thus lending itself to a higher level of regulation, especially at firms implementing DevSecOps. Companies use Fugue as the “single source of truth” when operating and managing their Cloud-based technical assets.
Fugue uses a classical music metaphor to describe its functionality. The programming language used in the application is called Ludwig. Individual programs are known as compositions, while the automation server is called the Conductor. Chef, another Cloud infrastructure management tool, uses food-based metaphors in a similar manner.
Ludwig offers a host of features suitable for software engineers, including types, code validation, and a module-based architecture, allowing complex designs to be broken down into individual abstractions. It facilitates collaboration as well as the documentation that is vital in a regulatory compliance scenario. Once again, this approach illustrates the blurring of technical roles which is a major aspect of DevOps itself.
Scenarios where using Fugue makes Sense
Organizations embracing DevOps with the hope of automating their Cloud operations make up the core of Fugue’s user community. It automates all aspects of CloudOps, including the creation, operation, and maintenance of any size infrastructure. As usage needs increase, the system scales in a seamless fashion – an important consideration in the modern technology world.
It also plays well with other DevOps tools used for Continuous Integration, including Jenkins, Travis, and CircleCI. This helps automate the entire lifecycle of any organization’s Cloud-based infrastructure. Ludwig compositions are also able to be stored in a source code repository, including Git and GitHub.
The tool truly shines in the management of Cloud-based infrastructures where cybersecurity and regulatory compliance are highly important. As noted earlier, Ludwig makes the creation of vital system documentation an easy process. Fugue supports traditional IT processes relevant to compliance, like change control and policy enforcement – all in an automated fashion.
Companies with an investment in container technology, such as Docker, also benefit from being able to easily create and manage virtual Cloud-based environments. Fugue includes a “no-op” operational mode to properly vet any infrastructure changes before they go live in production. Remember that everything gets documented and stored in source control
In short, Fugue needs to be considered as a valuable tool by any company who relies on the Cloud for their technical operations. It is especially useful for organizations embracing DevSecOps or that require strong regulatory compliance.
Keep returning to the Betica Blog for additional insights from the software development world. Thanks for reading!