Skip to content

Build a service map editor with React Flow, Elysia and Postgres - #474

Draft
sdairs wants to merge 2 commits into
mainfrom
codex/service-topology
Draft

sdairs wants to merge 2 commits into
mainfrom
codex/service-topology

Conversation

@sdairs

@sdairs sdairs commented Oct 5, 2026

Copy link
Copy Markdown
Collaborator

Build a saved service-map editor with React Flow, Zustand, ELK.js, Elysia on Bun, Eden Treaty and Drizzle. Users add, rename, connect, arrange and remove services; Postgres stores the graph as JSONB and commits each revision snapshot atomically. Stale tabs retain their draft and receive a visible conflict.

Includes pinned dependencies, SQL roles/schema/seed, a clickhousectl-based README, screenshot, and scoped build/unit workflow. The app is a trusted local demo with synthetic data and no accounts.

Validation ran inside an isolated OrbStack VM against local Postgres 18 and a disposable ClickHouse Managed Postgres 18 service: typecheck, build, five semantic tests, five database integration tests (concurrent revision saves, rollback, JSONB roundtrip, validation and restricted grants), and a Chromium editing/layout/save/reload/conflict workflow. Actual process restart preserved the exact saved graph. Verified managed TLS, unrelated-CA rejection, and reachable mismatched-hostname rejection through Bun SQL. The connector handles Bun 1.4.2 CA rotation bundles by retrying only supplied trust anchors while preserving hostname verification. Disposable managed service deleted and verified absent; VM stopped.

The companion article remains local and outside Git. ELK is loaded on demand; its lazy chunk still produces Vite’s large-chunk warning.

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