Eddie Harari writes: > 1. If i have the USA phone directory as my DB, and NY has 10,000,000 records > in it. or i have a DB with only NY 10,000,000 records without the rest of > the USA. searching for all NY records will take same time at both cases ?
>From my understanding, they will both run in the same time since the sharding >on data is based on the indexes and not on the "databases"/"tables". In this case the index is the same for NY so it should run in the same time. > 2. The other reason to split the DB is security, should a "bug" or a google > app exploit will be available you dont want > your customer "A" records be viewed by customer "B". the application > runs in somekind of sandbox but if the DB is one > any small error in program can expose everything to everyone. I don't have any real comments about this, but it feels to me like you're seeing this as a typical DB server isolated in one part, with all the data in the same place. One of the advantages provided by the Datastore is that that idea is no longer true. -- Federico Builes --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
