In addition to having a source control and proper branching process in place, What are the factors to consider/best practices if we decide to use a single environment across different teams irrespective of the teams working on the same set of API proxies or different.
Here are some of the things to consider if we decide to use a single environment across different teams
#1 API proxy name, Cache, KVM, target servers names should have their team names as the prefix. (Environment entities)
#2 We can have team specific virtual hosts too if the certs are a wild card or the ops team is responsible for creating the virtual hosts and provide them to the dev teams to avoid classification errors.
#3 App name, developer, company names should have their team names as the prefix. (org level entities)
#4 Externalize all the configurations. for example : config.json(dev binding) or KMVs. (runtime binding)
#5 If the teams are working on different API proxies, we don't need to worry about the base paths but if they are working the same proxy it will create base path conflicts. At least, the dev environment should be different.
Are there any other factors to be considered or any pros and cons?
LinkedIn
Twitter
