Solved: Replacing a custom-built API proxy application wit... - Page 2

padlco · 12-02-2021 05:54 AM

Hi,

I have an application deployed into Google App Engine. This application have a database in Google Cloud Datastore. To improve the performance, the data stored into Datastore, is stored in App Engine Memcache too. I would like to implement this in an Apigee X proxy and I have several questions.

- In terms of performance, is better option use Datastore with Service Callouts or use KVM as database?

- to support multi-region, are the KVM datastores in the same region that the Apigee Instance?

- do you think it is better option to to use Cache Policy or a MemoryStore instance of App Engine Memcache?

Thank you,

Regards.

dchiesa1

oh! you used the term "proxy" to describe the thing you have in AppEngine. Is it actually a proxy? If that's so, then I think you're correct - for better performance, scale, and capability, you can use the Apigee platform for your API Proxy purposes, and eliminate that thing you've built in App Engine. Apigee will do authentication, authorization, routing, and so on, associated to your APIs.

An example of data stored here would be users data needed to accept or reject the request to the API, the endpoints list that the consumer application can invoke, information about authentication mechanism that this proxy will use in the target API .

Apigee has its own Domain Specific Language. For all of the things you are describing, you can configure Apigee to perform that work. There is no need for an Apigee API proxy to use an external datastore like Cloud datastore to hold that configuration information. Apigee stores the configuration in its own internal datastore, which is multi-region as appropriate.

You might want to check out some Apigee 101 videos to get the idea for how you can configure Apigee to do authentication, routing, and so on.

View solution in original post

Replacing a custom-built API proxy application with Apigee - where is the config stored?