PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Git & CI/CD
Private GitLab Build & Deploy Pipeline Unit Tests Environment Variables Deploy Web Services Configure Web Services

Web Services (Docker + Container Orchestration)

Biztraak’s web-service workflows deploy containerized applications with provider-specific infrastructure, rollout, and health-check behavior. See Capabilities and Availability for the current provider differences. Auto-scaling is not a platform-wide default.

How it works

Blue/Green Deployments

  • Blue Environment: current production traffic
  • Green Environment: new version being deployed
  • Traffic Switch: the configured deployment path switches production traffic after validation
  • Rollback: rollback behavior follows the configured deployment path

Infrastructure Components

  • Container Orchestration: managed container hosting (ECS, GKE, AKS)
  • Load Balancer: traffic distribution and health checks
  • CDN: global edge caching and SSL termination
  • Container Registry: private image storage
  • Deployment Service: automated blue/green orchestration when the selected provider workflow exposes that strategy

Deployment Pipeline

  1. Container Build → containerize your application
  2. Registry Push → push images to your private container registry
  3. Deployment Service → trigger the provider rollout strategy configured for the service
  4. Health Checks → verify deployment success according to the configured strategy before any traffic switch

Blue/green deployment example

  1. Developer pushes commit to feature-login branch
  2. Configured pipeline runs in the execution environment selected for the project
  3. Container build creates container image from your application
  4. Registry push stores image in your private container registry
  5. Build Review environment may spin up when the project workflow is configured for it
  6. PR merged to main may trigger the configured production workflow
  7. For a blue/green deployment exposed by the selected workflow:
    • Green environment created with new container
    • Health checks run against green environment
    • Traffic switches once the configured health checks pass
    • The blue/green deployment path retains the previous capacity and can roll back on configured failure alarms
  8. Production live → your-app.biztraak-hosting.com serves new version
  9. Available audit records are updated with build and deployment context

Cloud Provider Examples

See Capabilities and Availability for the provider templates and runtime differences.

Monitoring & Operations

Deployment Monitoring

  • Real-time logs available in the configured pipeline interface
  • Cloud console shows deployment progress and status
  • Health check status visible in load balancer metrics
  • Rollback capability available for deployment strategies that support rollback

Auto-Scaling

  • CPU- and memory-based scaling: automatically adjust capacity based on demand
  • Target tracking policies: maintain optimal performance
  • Scheduled scaling: handle predictable traffic patterns

Security Features

  • Private container registry: built container images stored securely in your cloud account
  • IAM roles: least-privilege access for all components
  • VPC isolation: containers run in private subnets
  • SSL/TLS termination: encrypted traffic with automatic certificate management

Configuration Options

Click here to learn more about configuration options including:

  • Custom Ports: configure internal ports for load balancer health checks
  • Environment Variables: inject secrets and configuration at deployment time
  • Resource Limits: set CPU and memory constraints
  • Health Check Paths: customize application health endpoints
  • Scaling Policies: define auto-scaling behavior
  • Cloud Provider Selection: choose AWS or GCP based on your needs

Why choose Web Services?

  • Rollout options: use blue/green or other strategies where exposed by the workflow
  • Deployment foundations: use the load balancing, scaling, and health-monitoring options available for the selected runtime
  • Security configuration: use the registry, network, and IAM settings exposed by the selected provider workflow
  • Git integration: connect infrastructure and application workflows when the project exposes both paths

Next steps

Web services on Biztraak connect container builds to provider-specific deployment and operational workflows. Confirm the supported runtime, rollout strategy, scaling behavior, and network options before planning a production workload.