What is a Nexus Environment?
A Nexus Environment is a dedicated Redis-based data store with specific purpose and isolation. Nexus 3.0 is fundamentally a system of environments - each environment handles a specific domain of data.
Environment Architecture
Most environments follow the dual-pod pattern:
┌─────────────────────────────────────────┐
│ ENVIRONMENT │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ VAULT │ │ OPERATIONAL │ │
│ │ (Docker) │───▶│ (Native) │ │
│ │ Port 66X0 │ │ Port 66X1 │ │
│ │ Password │ │ Password │ │
│ │ Protected │ │ Protected │ │
│ └─────────────┘ └─────────────┘ │
│ WRITE READ │
└─────────────────────────────────────────┘
Vault Pod (Docker container): - Primary data storage - Write operations go here - Runs in Docker for isolation - Port ends in 0 (e.g., 6620)
Operational Pod (Native Redis): - Read replica of vault - Read operations go here - Runs natively for performance - Port ends in 1 (e.g., 6621) - Syncs from vault via Redis replication
Exceptions to Dual-Pod Pattern
Locker Environment: - Single vault only (port 6720) - No operational pod exposed - Contains sensitive credentials - Security isolation is priority
Some environments use vault-only: - Links (6635 only) - Workflow (6615 vault, 6616 operational but same password)