Skip to main content

CDPG Go developer portal

Build and review CDPG Go services from an empty repository through gateway exposure, authorization, event integration, local testing, and GitOps deployment. The portal combines an evidence-backed platform guide with a progressive Go curriculum.

Platform status: Partially implemented. The platform is before its first production release. Every architecture and integration page distinguishes implemented source behavior from planned target capability.

Choose your route

Starting pointRecommended route
New to programmingComplete the Curriculum modules and checkpoints, then the new-service tutorial
Experienced engineer, new to GoModule 0, Module 1 checkpoints, Modules 2–3 gaps, then Developer Guide
Experienced Go engineerFive-minute orientation, service standard, integrations, then tutorial
Service/platform/Data Plane/security/SRE reviewerSelect the role path in Learning paths

Learning outcomes

By the end you can:

  • write idiomatic, race-free Go with explicit error and context flow;
  • design a layered service whose business logic has no transport or driver imports;
  • use dx-common-go/platform for bootstrap, HTTP, SQL, cache, events, identity, errors, paging, and health;
  • secure a route through the gateway with OIDC, destination-bound workload identity, constrained subject propagation, and relationship authorization;
  • administer grants with dx-acl-go, consume current OpenFGA checks, and prepare safely for planned OPA policy;
  • enforce typed carried decisions in Data Plane services without accepting executable policy queries or calling the PDP per query;
  • test units, adapters, contracts, security boundaries, and full-stack flows;
  • deploy and operate a service through the platform's GitOps model;
  • submit a focused, evidence-backed contribution.

Start here

  1. CDPG platform orientation
  2. Current and target state
  3. Go service architecture standard
  4. Shared Go platform modules
  5. New service quick start

How the curriculum works

  1. Learn the concept and its failure modes.
  2. Read one current source example.
  3. Practice in a small exercise.
  4. Check your understanding without copying the sample.
  5. Verify with tests, race checks, or a running stack.

Authoritative references

The curriculum teaches. It does not duplicate reference documentation:

New Go learners start with Environment, then use the roadmap to track milestones. Service developers start with the learning paths.