Advantages and disadvantages of multiple namespaces in the application

I have checked a couple of links to understand what are the advantages and disadvantages of creating multiple namespaces in the application.

Apart from failover ability, it does not mention much about other resource management. Our app has two sub projects, we are planning to create only one namespace if it is all the same. Can you please clarify what are the scenarios one has to consider to go with separate namespaces?

If these subproject are fully independent then I would use a namespace per project. Then they don’t need to think about name and workflow ID collisions. Various options like retention period are configured per namespace. Throttling limits can be set per namespace as well. So if some of the services starts exceeding the configured limit all services that share namespace with it get throttled.

1 Like