Skip to content

Add NestJS shipment tracker with PostgreSQL transitions and CDC reports - #452

Draft
sdairs wants to merge 1 commit into
mainfrom
codex/shipment-tracker
Draft

sdairs wants to merge 1 commit into
mainfrom
codex/shipment-tracker

Conversation

@sdairs

@sdairs sdairs commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Adds a small account-scoped NestJS shipment API using TypeORM and ClickHouse Managed Postgres. Expected revisions and account-wide retained request IDs coordinate lifecycle transitions: state and immutable event commit together, matching retries return the original event after later transitions, and conflicting requests return 409. Shipment creation remains a seed/admin operation.

ClickPipes replicates only accepted events to analytical ClickHouse. The read-only official Node client reports bounded daily transition/delivery aggregates using typed parameters, FINAL/tombstone reconciliation and string-valued 64-bit results. Operational transitions remain available when analytics lags or reporting access fails.

Validation: fresh native Linux npm install, typecheck/build and four unit controls; real Cloud migrations/reversal/repeatable seed; simultaneous revision race and ten matching requests; ownership/input/body/pagination checks; forced event-insert rollback; genuine process restart; restricted roles and verified/negative TLS; snapshot/CDC, pause/resume, analytical outage/recovery, keyed tombstone/restoration and exact per-account report equality. Private evidence and the companion article remain outside this PR. Resources are temporary and cleaned after independent review; no Cloud credentials in CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant