Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor TS Docs #278

Merged
merged 16 commits into from
Jan 7, 2025
Merged

Refactor TS Docs #278

merged 16 commits into from
Jan 7, 2025

Conversation

kraftp
Copy link
Member

@kraftp kraftp commented Jan 6, 2025

  • Move the most important TS docs (workflows, steps, transactions...) back to the top level
  • Improve and condense their text using material from the Python docs

@kraftp kraftp marked this pull request as draft January 6, 2025 23:16
@kraftp kraftp marked this pull request as ready for review January 7, 2025 01:09
{
from: '/typescript/tutorials/configured-instances',
to: '/typescript/tutorials/programmingmodel/configured-instances',
to: '/typescript/tutorials/development/configured-instances',
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think this belongs in the "development" section. Maybe the point of the "development" section was missed. The programming model bit was supposed to be about what your code says and how it works, loosely, "coding". The "development" section was supposed to be about supporting tools and techniques. Configured instances is a coding construct.

These guarantees assume that the application and database may crash and go offline at any point in time, but are always restarted and return online.

1. Workflows always run to completion. If a DBOS process crashes while executing a workflow and is restarted, it resumes the workflow from the last completed step.
2. [Steps](./step-tutorial.md) are tried _at least once_ but are never re-executed after they complete. If a failure occurs inside a step, the step may be retried, but once a step has completed, it will never be re-executed.
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if it is worth saying something like "completed (returned a value or thrown an exception to the calling workflow)". Some people seem to assume "completed" means "completed successfully" but it doesn't of course.

@chuck-dbos chuck-dbos self-requested a review January 7, 2025 13:38
@chuck-dbos chuck-dbos merged commit 3e6cd73 into main Jan 7, 2025
1 check passed
@chuck-dbos chuck-dbos deleted the kraftp/pm-refactor branch January 7, 2025 13:39
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