The general rule is optimize for your primary use case, denormalise to support others. In addition, enforce and support constraints In your code.
If your primary case is restaurant search, embed and index all necessary data. This will be the fastest solution and easiest to work with On Appengine extra data doesn't cost you unless it's indexed. There is a careful balance between optimising for speed, cost and transactional integrity. My advice is if this is your first go, expect to make mistakes and to need to reengineer your data a couple of times. Make that process as easy as possible. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/8b119b09-40bf-40a7-b798-c0b63e61ebab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
