ENGINEERING NOTES
Architecture notes and production practice.
Selected write-ups from the Cloud GIDO team on open infrastructure—covering product architecture and production troubleshooting to help you evaluate capabilities, boundaries, and adoption paths.
Notes are written in Chinese. Other locales show English titles and summaries for easier browsing.
FEATURED
DolphinScheduler on K8s: TaskInstanceLogPath is empty
Hostname resolution and Worker registration failures that look like empty log paths.
Read note →Doris BE periodic restarts: RScan threads exhausted pids.max
A production field note: sawtooth thread growth, false Routine Load blame, and layered remediation.
Read note →GIDO Batch feature map: Studio, DAG, scheduling, quality, lineage
Batch reliability is less about writing SQL and more about orchestration, instances, alerts, and governance.
Read note →GiRisk: six capabilities behind millisecond decisions
Rules, exposure, limits, audit, and replay are first-class product features—not slideware.
Read note →GISO: turning fragmented tracking into executable contracts
Schema, multi-end SDKs, gateway validation, and quarantine form a closed loop for trustworthy events.
Read note →Why a full stack still feels hard: the missing control plane
Kafka, Flink, Doris, and Kubernetes can be in place while teams still struggle with fragmented development, untrusted events, and opaque decisions. Cloud GIDO addresses the control plane.
Read note →GIDO, GISO, and GiRisk: how the feature sets divide
A practical matrix of responsibilities across data workloads, event contracts, and real-time decision evidence chains.
Read note →Need an architecture review?
If these notes map to your stack, talk with an engineer about boundaries, deployment, and a focused verification path.