No matter how you built your cloud—no matter what tools or services you’ve used to provision an application’s infrastructure—you can migrate existing workloads to Fugue easily and securely with no downtime. At AWS re:Invent this week, November 27 - December 1, test out Fugue’s automated infrastructure governance with our team at booth 1600 or explore Fugue’s new migration, enhanced compliance capabilities, and other features in the latest product release.

Fugue reduces the cloud's new kinds of undifferentiated heavy lifting—the generic, often complex cloud work every business has to contend with—in a single system that delivers control, visibility, and speed for application governance. Reducing the lift is baked into every part of Fugue, including the first step, installation. With Fugue, no preliminary, extra layers of infrastructure creation, care, and feeding are required to get started. One command bootstraps everything!

Whether businesses are using cloud providers, on-premise data centers, or hybrid setups to host web services and backends, infrastructure failures are a fact of life. They have to be on our radars as a matter of routine. This makes architecting for failure and for the future, from the start, among the most pressing imperatives for business IT departments. The next five years will see the rise and democratization of centralized control systems for cloud ops with fault tolerance architected into the very fabric of those systems. (This article was first published in DZone's Cloud Zone on April 3, 2017.)

For Fugue, providing documentation is about more than just creating a high-level reference for information. Our documentation content ranges from examples of creating complex infrastructure with Fugue to walkthroughs of integration with a number of popular devops tools in use today. Which is what we’re here to talk to you about.

A CMDB for APIs is a crucial aspect of Fugue, and one area where running your operations with Fugue offers a lot of value to you. Fugue's CMDB is an effect of our declarative model for configuration, built around our typesafe, compiled Ludwig language. Once it is run as a process in Fugue, that declaration is made real and immutable with machine precision.

Fugue uses a new domain-specific language, Ludwig, to describe infrastructure configuration. Before we started building, we looked around for what we wanted, but didn't find it all in one place. We want typical things you do in cloud to be easy, and not feel like programming. We want users to get great error messages, fast. We want a program that compiles to almost always work in the cloud. We want sophisticated work to be possible, but safe, predictable, and shareable.

Our system is made up of a collection of services engaging in sophisticated interactions. It became obvious early on that testing manually would only get us so far. Here are some insights that have proven useful as we transitioned from a mostly manual work mode to a mostly automated one in QA testing.