Skip to content

docs: README disambiguator + rework Architecture for duroxide/duroxide-pg layering#193

Merged
tjgreen42 merged 3 commits into
mainfrom
docs/duroxide-family-readme
May 29, 2026
Merged

docs: README disambiguator + rework Architecture for duroxide/duroxide-pg layering#193
tjgreen42 merged 3 commits into
mainfrom
docs/duroxide-family-readme

Conversation

@tjgreen42

@tjgreen42 tjgreen42 commented May 29, 2026

Copy link
Copy Markdown
Contributor

README changes that clarify how pg_durable relates to duroxide-pg and includes duroxide-pg in the Architecture section.
See also:

tjgreen42 and others added 3 commits May 28, 2026 21:35
Adds a single-blockquote callout near the top of the README so a reader
can immediately tell pg_durable apart from duroxide-pg. Replaces the
earlier draft that added a full "Duroxide family" overview here; the
overview is now kept only in the duroxide hub README.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The previous Architecture diagram glossed over duroxide-pg entirely and
mislabelled the durable runtime tables as 'duroxide internals' inside the
df schema. Update the section to:

- Name duroxide (orchestration runtime) and duroxide-pg (PostgreSQL state
  provider) explicitly and describe what each contributes.
- Replace the diagram with a precisely-aligned nested view showing
  pg_durable -> duroxide -> duroxide-pg -> PostgreSQL, plus the actual
  schemas (df.* for DSL graphs, duroxide.* for runtime state).
- Fold the 'which to pick' guidance (formerly its own 'Relationship With
  duroxide-pg' section) into the Architecture section as a trailing note,
  framed correctly: pg_durable is built on top of duroxide and duroxide-pg,
  not an alternative to them.

Also fix two stale items in the old diagram: 'durable.if()' -> 'df.if()'
and dropping the misleading '(duroxide internals)' label on the df schema.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@tjgreen42

Copy link
Copy Markdown
Contributor Author

@tjgreen42 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree [company="{Microsoft}"]

@tjgreen42

Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

@pinodeca pinodeca left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me: a clear improvement in clarity/detail.

@tjgreen42 tjgreen42 merged commit ebf2de9 into main May 29, 2026
4 of 5 checks passed
@pinodeca pinodeca deleted the docs/duroxide-family-readme branch June 4, 2026 19:01
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.

2 participants