Wercker is a genuinely cloud-native platform.

And no, no, we're not just saying that because it's a buzzword. Let us explain what cloud-native means and how Wercker achieves it.

Defining Cloud-Native

To be a truly cloud-native application, in practical terms, your app needs to: be built to provide a business-valuable feature, leverage CI/CD (continuous integration and continuous delivery) for its testing and deployments, and run in a standardized container. Additional bonus points if it's built using an Agile Methodology (like SCRUM) and is at least inspired by the Twelve Factor App methodology.

The benefits of being cloud-native come down to resilience, as every app instance is deployed from the same base container image, and scaling is handled by the container orchestration layer. This allows things that were impossible in the past without major investments—like having an application run on multiple private and public clouds at the same time, and the ability to bring more into the mix without any application changes.

Cloud-Native Architecture

The following image illustrates a cloud-native architecture:


Cloud-Native Apps on Wercker

Wercker knows cloud-native apps, as the entire Wercker platform is built using these principles. They allow clients to incorporate Wercker to be the continuous integration and delivery pipeline that will build, test, and create the standard container image that is used as a base for deployments. In addition, Wercker’s pipeline integrates with Kubernetes to handle the deployment and initial setup of your app via its container image, and will run on multiple cloud providers, including Google Compute, Microsoft Azure, and Amazon Web Services.