Is there a best practice entity design for storing Membership data
that targets a global market? Ideally, the Membership data is
partitioned geographically since a Membership in the U.S. is
independent of one in the U.K. and elsewhere, for example. The motive
is that operations (searches, inserts, updates, deletes) on U.S. data
need NOT involve data from the U.K. and elsewhere. Can GAE
transparently provide this based on the design of a single Membership
Entity or do you have to create separate Entities for each region in
your design such as MembershipUS, MembershipUK, etc?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en
-~----------~----~----~----~------~----~------~--~---
