Deployment
When you deploy using Defang, whether it's with defang compose up with a Compose file or using a Pulumi program, Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in Defang BYOC or ours in Defang Playground), build the image, and store it in the cloud provider's container registry.
Deploying Updates
When you run a deployment to update one or more services, Defang will build new images for your services, and provision new resources to replace your existing services.
Zero Downtime Deployments
Defang can deploy your services using different modes. When using the production mode, Defang will make sure the new replacement services are healthy before deprovisioning your existing services.
By default, using the development mode, Defang will deprovision your existing services before provisioning replacements. This helps reduce costs.
In Defang BYOC, Defang uses your cloud provider account to build and store your images. In Defang Playground, we build and store your images for you.
Deployment Modes
As mentioned above, Defang offers different deployment modes: development, staging, and production. You can switch the modes using the --mode CLI flag.
Workloads with GPUs do not support zero downtime deployments. If you have a workload with a GPU, you will experience downtime during updates.
Instance Types
Defang defaults to "spot" instances. This is a cost-effective way to run your workloads, but it does mean that your workloads can be interrupted at any time. This is consistent with the 12 Factor principle of disposability.
In the future, we may provide a way to use "on-demand" instances for workloads that require more stability.