Obiente Cloud can be deployed in several ways, from simple local development to fully distributed production environments.
Best for: Local development, testing, single-server deployments
- Single PostgreSQL instance
- Single Redis instance
- Simple to set up
- Good for development
Best for: Small production deployments, minimal HA requirements
- Single PostgreSQL (Swarm-managed)
- Single Redis (Swarm-managed)
- Distributed across nodes
- Basic redundancy
Best for: Production environments requiring maximum uptime
- 3-node PostgreSQL cluster (Patroni + etcd)
- 3-node Redis cluster
- Automatic failover
- Full HA capabilities
- ✅ You're developing locally
- ✅ You have a single server
- ✅ You don't need redundancy
- ✅ You want the simplest setup
- ✅ You have 2-3 nodes
- ✅ You want basic redundancy
- ✅ You don't need full HA
- ✅ You want distributed deployments
- ✅ You have 5+ nodes
- ✅ You need maximum uptime
- ✅ You require automatic failover
- ✅ You're running production workloads
| Feature | Docker Compose | Swarm Simple | Swarm HA |
|---|---|---|---|
| Nodes Required | 1 | 2+ | 5+ |
| PostgreSQL | Single | Single | 3-node cluster |
| TimescaleDB | Single | Single | 3-node cluster |
| Redis | Single | Single | 3-node cluster |
| Auto Failover | ❌ | ❌ | ✅ |
| Load Balancing | ❌ | ✅ | ✅ |
| Metrics HA | ❌ | ❌ | ✅ |
| Setup Complexity | Low | Medium | High |
| Resource Usage | Low | Medium | High |
All deployment methods require:
- Docker 24.0+
- Linux OS (Ubuntu 22.04+ recommended)
- 4GB+ RAM
- 20GB+ disk space
For specific requirements, see Requirements.
Choose your deployment method and follow the respective guide: