Skip to main content

Single-App Deployment

Did you know?

SDR requires additional enablement and licensing. Contact your Atlan representative for details.

Single-app deployment is the SDR lifecycle mode where each connector app is its own deployment unit and you own the full lifecycle. There's no orchestrator in between—you install, upgrade, and stop each app yourself using docker compose or helm install. For the other mode, see SDR Orchestrator. For a side-by-side comparison, see App Lifecycle Modes.

Architecture​

Each app is a self-contained container bundle that includes everything needed to run a connector:

  • Temporal worker:polls Atlan over outbound gRPC and executes extraction workflows
  • Dapr:abstracts access to object storage, secret store, and Atlan's event ingress
  • Application code:source-specific extraction logic
  • FastAPI server:handles in-app HTTP requests

The app runs either as a Docker container (Docker Compose) or as a Helm release in a Kubernetes namespace. There's one deployment unit per connector app—separate apps don't share a process or a container.

For shared component details that apply to both lifecycle modes, see Core Architecture.

What you manage​

In single-app mode, every operational step is yours, per app:

  • Install:generate OAuth credentials, fetch deployment artifacts from Atlan, fill in configuration, and run docker compose up or helm install.
  • Start and stop:manage the container or Helm release with your existing tools.
  • Upgrade:pull the new app image and redeploy. Temporal's durable execution resumes in-flight workflows once the new app is running.
  • Credential provisioning:generate and rotate OAuth client credentials for each app.
  • Configuration:maintain the docker-compose.yaml / values.yaml and any environment or secret store settings.
  • Monitoring:collect logs and metrics from each app using your existing observability stack.

Each app runs independently—updating one app doesn't affect the others.

Supported platforms​

Single-app mode works on both supported SDR platforms:

Both platforms use the same app container images—only the deployment wrapper differs.

When to choose single-app mode​

Single-app mode fits when one or more of these apply:

  • You're evaluating a single connector and want the fewest moving parts.
  • You already manage deployments through IaC or GitOps and want app versions pinned in code.
  • You need full manual control over every install, upgrade, and rollout.
  • Your environment standardizes on a specific deployment workflow (for example, Argo CD, Flux, or Terraform) that you want to reuse for SDR apps.

When to consider orchestrator mode instead​

If you're deploying several connectors and want installs, upgrades, and credential provisioning driven from the Atlan UI, consider SDR Orchestrator instead.

See also​