Apigee Edge configuration for read API / write API

[oyamatakuro]

Hello,

I think API has two kinds.

One is read API, which just reads data and the other is write API, which update data.

I was asked that there are any difference or consideration between read API and write API in terms of the settings or tuning of Apigee Edge.

Any information would be appreciated.

Thanks,

[DChiesa]

There is no difference in configuration for Apigee Edge. There are some considerations.

In the case of a "write" API, I suppose you are referring to http verbs PUT, POST, and possibly DELETE.

In the first two, your API must handle message payloads. Apigee Edge acts as a reverse proxy, so this is done automatically. You can add in message transformation policies (for example transforming JSON payloads to XML, or similar), but those steps are optional.

A "read" API I suppose is always an HTTP GET. If you like, you can apply the Apigee ResponseCache policy to cache GET results.

If you are using OAuth2.0 tokens to allow access to the API, then you may wish to apply different scopes to the tokens in order to allow reads or writes.

[oyamatakuro]

Thank you for your answer!