System Design

Infrastructure

How Datain works end-to-end: from control plane decisions to runtime provisioning and low-latency data delivery.

Working Mechanism

Datain separates decisions from execution. The control plane handles policy and placement, while the data plane runs close to hardware with deterministic scheduling. This design keeps operations predictable under heavy concurrency.

# Runtime selection pseudocode

if workload == "burst" -> container
if workload == "steady_db" -> lightweight_vm
if workload == "latency_critical" -> manster_kernel

Control Plane Decision

The scheduler inspects workload shape, durability requirements, and latency target to choose the correct runtime layer.

Runtime Provisioning

Compute is created as a container, a dedicated lightweight VM, or a direct Manster Kernel profile with storage mappings.

Data Path Activation

Traffic enters through regional ingress, then reaches the chosen runtime with WAL, replication, and health signals enabled.

Adaptive Optimization

Telemetry feeds back into the control plane to rebalance CPU, IOPS, and memory pressure in real time.