Overview

Darwinium operates by deploying edge workers to your CDN. These workers are bespoke bundles that are created whenever a change is made to your journey or risk decisioning logic. For each step in your journey, a bundle is created which is then assigned to a route on your CDN.

 When a change is pushed to the main branch of a node’s git repository, an automated build process is invoked to create edge artifacts that are aligned to the push’s last git commit hash. Builds are then deployed to customer infrastructure using Darwinium’s inbuilt deployment manager, or manually using a customer CI/CD process.  

 Each build artifact kept by Darwinium, enabling rapid rollback of deployment to a given build.

Darwinium’s inbuilt deployment manager

Out-of-the-box, Darwinium provides its own deployment manager that can streamline edge deployments. This is accessible to Darwinium portal users with manage deployment permissions (see: Permissions and Access Control) by navigating to admin > nodes and then clicking next to the appropriate node.

Each commit that has been built successfully may be deployed to CDN infrastructure using the “deploy” button to the right of the build.

A commit highlighted in green denotes the build that is currently active.

Using your own deployment process

Darwinium provides a flexible deployment system that enables external infrastructure processes to coordinate deployment of edge assets. For more information see: Controlling Darwinium's deployment using Terraform

Alternative Deployments

See: CDN-free Darwinium implementations