Recommend usage of Namespace

tihomir · April 12, 2022, 5:37pm

If you have projects that are fully independent from one another, using one namespace per project is a good approach.
In this case you do not have to worry about workflowId collisions between these applications as well as can set different configurations such as retention periods, archival, and throttling limits per application as those are set per namespace.

See also some related threads here and here.

Topic		Replies	Views
Namespace Design Community Support namespace	1	751	November 3, 2021
Advantages and disadvantages of multiple namespaces in the application Community Support java-sdk	1	1346	July 21, 2021
What are best practices for organizing namespaces? Community Support general-impl , namespace	1	977	July 22, 2022
Cost of creating a namespace Community Support namespace	4	1047	April 10, 2022
About the implications of running child workflows in a different namespace than the parent Community Support	2	1141	March 31, 2023

Recommend usage of Namespace

Related topics