-
Notifications
You must be signed in to change notification settings - Fork 2
Convention suggestions
Ognjen Katić edited this page May 16, 2022
·
6 revisions
These are some of the conventions that were observed to give better results, but they are by no means definite and any suggestions are welcome.
-
Prefix workflow and task names with the domain they are dealing with. Since conductor is a microservice orchestrator it is easy to create name conflicts if you stick to names like validate_input.
-
Use validation attributes for request model properties to make the handle method lighter.
-
Keep request and response models in the same file with the worker if you plan on having a lot of workers. This is usually not good, but the number of files can make the project hard to navigate.