Recommend usage of Namespace

We want to use namespace to partition dev environment for different teams/developers as suggested from here, but I also read from here that we should avoid it. Can someone clarify if this is a good practice?

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.

1 Like