Deployment Topology
Architecture-level view of DALP deployment topology covering environments, runtime zones, network boundaries, and scaling constraints. Links to self-hosting guides for installation procedures.
Purpose
Architecture-level view of how DALP components are deployed, organized, and scaled across environments.
- Doc type: Reference
- What you'll find here:
- Runtime zones and component placement
- Environment types and their purposes
- Network boundaries and traffic flow
- Scaling constraints and bottlenecks
- Related:
- Component Catalog — full component inventory
- Self-Hosting — installation procedures
- Operability — observability and database architecture
Runtime zones
DALP components deploy across three runtime zones:
| Zone | Components | Network exposure |
|---|---|---|
| Frontend | Asset Console (React SPA) | Public internet via CDN/reverse proxy |
| Backend | Unified API, Execution Engine, Restate, Chain Indexer, Feeds | Internal network, API exposed via ingress |
| Data | PostgreSQL, Restate state store, blockchain nodes | Internal only, no public exposure |
Environments
| Environment | Purpose | Blockchain |
|---|---|---|
| Development | Local development with Docker Compose | Anvil (local EVM) |
| Staging | Integration testing with realistic data | Testnet (Sepolia, Amoy, etc.) |
| Production | Live operations | Mainnet or private network |
All environments use identical container images. Configuration differences are environment variables only.
Component deployment model
| Component | Runtime | Scaling model | State |
|---|---|---|---|
| Asset Console | Container (Node.js SSR) | Horizontal (stateless) | None |
| Unified API | Container (Node.js) | Horizontal (stateless) | Database sessions |
| Execution Engine | Restate runtime | Single-writer per workflow | Restate journal |
| Chain Indexer | Restate service | Single instance per chain | PostgreSQL checkpoints |
| Key Guardian | Container (Node.js) | Horizontal | External (HSM/custody) |
| Chain Gateway | Container | Horizontal | Health check state |
| PostgreSQL | Managed database | Vertical + read replicas | Persistent |
| Blockchain Node | Container or managed | Per-network | Chain state |
Network boundaries
Three boundaries separate trust zones:
- Internet → Frontend zone: TLS termination, rate limiting, WAF
- Frontend → Backend zone: API authentication, session validation
- Backend → Data zone: Database credentials, RPC node access
Blockchain RPC traffic exits the backend zone to external or co-located nodes through the Chain Gateway.
See also
- Self-Hosting for installation procedures
- Failure Modes for degradation behavior
- Database for data architecture
Quality Attributes
Quality attributes treated as first-class architectural requirements in DALP, with explicit tradeoffs and measurable commitments for security, reliability, performance, and regulatory compliance.
Data Domains
Data domain ownership map for the DALP platform showing sources of truth, data lifecycle stages, and governance boundaries across on-chain and off-chain storage.