Apigee BaaS serves as my backend for a prototype app. But somehow it's slow. Now I would want use Apigee cache to speed up the app. How do I go around doing it?
You can start from here : http://apigee.com/docs/api-services/content/why-use-cache. Let us know if you have any specific questions.
Hi,
If you're already using/exploring Apigee Edge, I can offer pointers to where caching is explained in the Edge documentation. I'd recommend starting there.
If you're already using Apigee Edge then you can add cache policies to populate a cache and look up values. Take a look at the General purpose caching topic in the docs for examples. You can also easily cache response data using the ResponseCache policy. Here's a sample implementation that you can easily deploy and try out.
If you're interested in proxying your API with Apigee-127 (Node.js approach), you can configure caches, as explained here.
@wwitman using Apigee Edge or any proxy would mean another http call (app->edge->baas). We are working on a mobile app that's got to work even on EDGE networks. Hence, I was looking at a BaaS level cache. With user management built into BaaS, this is perfect for our app. It's only the cache we have to figure out now.
Can you provide a couple sample calls that are slow? In general, GETs to API BaaS should be quick, but they can slow down considerably if you are, for example, passing a query with a large set of params.
Thanks @Steve Traut Please see my comments to wwtiman
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |