Skip to content Skip to sidebar Skip to footer

How To Use Endpoints For Android With App Engine Search Api

I will need to store a lot (anywhere from 100k to 10 million) longitude/latitude (geo)points with some extra variables attached. When the user logs in to my Android application it

Solution 1:

  1. The combination does make sense. App Engine as a platform is so powerful exactly because you have access to so many APIs and services like search API and enhancements to your workflow like the Endpoints system, instead of simply defining an API servlet and your own protocol (or implementing jsonrpc2.0, for example)
  2. Yes, you can use an endpoint API function to run any kind of code you could run anywhere else in your app. You could have your endpoint getNearbyPoints (GeoPoint p) function run a search API query and return the results. In order to link this all together, I'd recommend storing the full data (you mentioned there is lots of metadata) for a point in Datastore as an entity, but in the corresponding "document" in the search API, storing only the Datastore ID of this entity, so that your endpoints API function code can use the search API to query by distance from point p, then convert the results into full objects to send back.
  3. You could take a look at these additional resources. Not sure if you've read any or all of them, but they contain valuable info anyways.

Post a Comment for "How To Use Endpoints For Android With App Engine Search Api"