Fugue

How Whisker Labs Protects Consumer Data and Streamline Compliance in the Cloud

The importance of PCI compliance when moving to the cloud.

If you’ve been looking for information on unit testing and how to put it into practice, you’re in the right place. This post explores evaluating your code to determine what to test, understanding how to break your code into smaller functions, and creating your tests. It also covers rudimentary mocking, which is the practice of writing pretend calls to test your code against predictable values.

It’s never been easier or faster for companies using the cloud to deploy infrastructure on AWS. But, typically, you can’t move fast without compromising security, compliance, and control. Cloud infrastructure governance is an approach that protects enterprises. Only resources adhering to established policies and controls can ever be created, and compliance is guaranteed for the entire lifecycle of a given resource.

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's new Composer maps your application’s cloud infrastructure with automated, interactive diagrams that show your whole system in real time and the relationships between system components. You can zoom and inspect. You can quickly discover configuration errors and compliance violations. It's introduced with Fugue’s Transcriber—your tool to scan existing AWS cloud services in an account and automate their translation for easy Composer mapping. It doesn’t matter how you stood those services up. You'll see everything with Fugue. The new features are in beta and they're free.

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!

As a follow up to Python Mocking 101: Fake It Before You Make It, this post covers some higher-level software engineering principles demonstrated in our Python testing over the past year and half. In particular, the idea of patching mock objects in unit tests is revisited and explored in greater depth.

Fugue now supports the Amazon Web Services (AWS) GovCloud region, which means federal agencies, like enterprises, can automate operations in the cloud fast, while simultaneously meeting regulatory demands. Fugue deployments start with powerful, but easy-to-understand code declarations in a composition that governs a system’s infrastructure. By including select libraries in that composition with simple import statements, a particular agency’s compliance regime gets integrated from the start. This kind of fully realized policy-as-code provides a scalable protocol for agency cloud ops and increases speed to mission.

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.)