ADS Integration - Questions

[ankibatr]

Context

Integrating ADS into existing Python microservices on Kubernetes. Current service is a FastAPI application with PostgreSQL as backend storage for application data. After reviewing docs and deployment options, seeking architectural guidance on key decisions.

Core Architectural Questions

1. Deployment Topology

Option A: Separate services (Directory + Zot as independent kubed services)
Option B: Sidecar pattern (co-located containers in single pod)
Option C: Integrate into existing service (Directory SDK embedded in current Python service)

Question: For enterprise environments with ~500 agent records and moderate load, which pattern provides best balance of operational simplicity vs. resource efficiency?

2. Zot Registry Architecture

After reviewing codebase, unclear on Zot's role:

• Storage relationship: How does Zot registry storage relate to Directory's /data CAS storage?
• Necessity: Can Directory operate with PostgreSQL backend without Zot, or is Zot integral?

Research Done

• Reviewed: Architecture docs, deployment options, install/docker, SDK examples
• Analyzed: ghcr.io/agntcy/dir-apiserver:v0.4.0 deployment patterns

Seeking

• Production deployment pattern recommendations
• Zot registry clarification and requirements

Any insights from enterprise Directory deployments would be appreciated, particularly around deployment topology decisions and Zot registry integration.