Hi all, I have an unusual data retrieval requirement which cannot be fulfilled by the built-in indexing mechanism of the GAE (or any other Cloud platform for that matter). This got me thinking about managing my own index tables and just using barebones GAE indexing for retrieving individual entities from the Datastore by key. The new Mapper API offers distinct possibilities.
Yes, I realise that this almost sounds like an "App Engine" within an App Engine but please humour me a little: Outside of framework integration issues, my main concerns are cost and performance: 1. Will my indexing-related CPU cycles have a similar cost overhead to using the GAE's built-in indexing? 2. What about record retrieval (e.g. thousands of items), cursors, etc? 3. How do I maintain index consistency, transaction control, etc. I suppose these questions can be distilled down to one: Sitting higher up the stack, is my code at a serious disadvantage compared to the GAE internals when it comes to indexing control? ...and as an afterthought, might it be a good idea in general for applications to have this level of control over their indexes? I'm thinking of the many problems which frequently crop up with GAE indexes which are of course part of a massive indexing super-structure encompassing all apps? TIA -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
