Skip to main content
A single Cloud Adapter process receives origin-cloud API calls and translates them to native target services.A single Cloud Adapter process receives origin-cloud API calls and translates them to native target services.
The single binary deployment runs one service adapter process. It is the smallest useful operating shape: one endpoint, one process to supervise and one configuration to manage.

​
When to use it

Use a single binary for local development, evaluation, low-volume workloads or a service where process-level redundancy is provided by the surrounding platform. “Single” describes the adapter process, not the durability of your data.

​
What you operate

  • The adapter binary and its runtime configuration.
  • The endpoint and network path used by callers.
  • Runtime credentials and access to destination services.
  • Backend data, backups and recovery procedures.
For production, place the process under a supervisor and exercise restart and backend-failure recovery before sending traffic.

​
Move to a cluster

When one process is no longer enough for availability or throughput, keep the same service configuration and move to Cluster. Validate shared state, connection limits and rollout behavior before switching traffic.