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.

Sign up for GitHub

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

Jump to bottom

Add guidance on saga naming conventions #6899

Open

andreasohlund opened this issue Nov 6, 2024 · 0 comments

Member

andreasohlund commented Nov 6, 2024 •

edited

Loading

As discussed in #6894 (comment) we should consider providing guidance on naming sagas, saga state, timeout etc

Ideas:

Prefer names that are meaningful to the business, eg. "ShippingPolicy" instead of "ShippingSaga"
When to a thing is a "Policy" vs "Workflow"
How should the saga data class be named
- Should the class that defines the saga state be a nested class to the saga or not
Should timeouts be defined as a nested class or not

andreasohlund mentioned this issue

Feedback: 'NServiceBus sagas: Saga basics' #6894

Closed

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