After playing with Apigee a bit more, it seems that there's quite a bit of freedom for naming and configuring products, urls and proxies. What are some best practices for Apigee Edge? Do you use lower or upper case for naming proxies and products? What best practices do you have for using proxy policies? Do you tend to use pre-flow / post-flow or proxy vs target endpoints? Do you always have a public proxy that all developers can register, but require approval for the other products? What are some design patterns that you use when working with Apigee Edge? Do you try to use the API to keep track of changes and store things in revision control?
Solved! Go to Solution.
Dear @José Cedeño ,
What are some best practices for Apigee Edge ?
Do you use lower or upper case for naming proxies and products ?
Do you tend to use pre-flow / post-flow or proxy / target endpoints?
Do you always have a public proxy that all developers can register, but require approval for the other products ?
What are some design patterns that you use when working with Apigee Edge?
Do you try to use the API to keep track of changes and store things in revision control ?
Cheers,
Anil Sagar
Dear @José Cedeño ,
What are some best practices for Apigee Edge ?
Do you use lower or upper case for naming proxies and products ?
Do you tend to use pre-flow / post-flow or proxy / target endpoints?
Do you always have a public proxy that all developers can register, but require approval for the other products ?
What are some design patterns that you use when working with Apigee Edge?
Do you try to use the API to keep track of changes and store things in revision control ?
Cheers,
Anil Sagar