Policy Guidelines for specific use cases

Not applicable

I see there is quite documentation provided by Apigee specially about each policy. It provides each policy's description and possible use case. However, what I am missing is a kind of guidelines (best practices) where it shows (possible known) use cases and present their possible solutions (policy or composition of policy). This is helpful because usually customers they have their use cases (which is mainly common among most of them, like mashing different APIs, data mapping, etc.) and they want to look to that document (guideline) to see possible implementation of that use case.

Solved Solved
0 1 1,037
1 ACCEPTED SOLUTION

Hi Mohammad -

Thanks very much for the question. We're in the process of identifying more of the type of use cases you're asking for. In the meantime, we have a couple of cookbook topics and samples if you haven't seen them. Both have accompanying code in Github.

Mashup using policies: http://apigee.com/docs/api-services/cookbook/using-policy-composition

Mashup using JavaScript: http://apigee.com/docs/api-services/cookbook/implementing-http-clients-javascript

Both are also listed on our Samples reference page: http://apigee.com/docs/api-services/content/samples-reference

Beyond those, if you have any specific use cases you'd like to see documented, please let us know and I'll add that to our doc to-do list.

Thanks!

Floyd

View solution in original post

1 REPLY 1

Hi Mohammad -

Thanks very much for the question. We're in the process of identifying more of the type of use cases you're asking for. In the meantime, we have a couple of cookbook topics and samples if you haven't seen them. Both have accompanying code in Github.

Mashup using policies: http://apigee.com/docs/api-services/cookbook/using-policy-composition

Mashup using JavaScript: http://apigee.com/docs/api-services/cookbook/implementing-http-clients-javascript

Both are also listed on our Samples reference page: http://apigee.com/docs/api-services/content/samples-reference

Beyond those, if you have any specific use cases you'd like to see documented, please let us know and I'll add that to our doc to-do list.

Thanks!

Floyd