Diomedes, I wonder if you can spread the load in some way. For example
- a report application that grabs the data via api calls to a data store app, does processing and shoves it in memcache. - a set of capture apps that collect data in batches and then use api calls to the data store app to dump the data - you could even shard the data store app by segmenting the data. The capture and report apps would write to the appropriate data store. each customer then gets their own 3 separate apps (capture, store and report) which should keep costs as low as possible. If required you can have multiple versions of each layer. Obviously key problems are complexity (but clean REST API's should keep that to a minimum) and time lag between capture and report. Just an idea of the top of my head (and you would need to check terms of service would be ok with this). Dave -- Dave Warnock: http://42.blogs.warnock.me.uk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
