Because if you have denormalized data, then record updates can become enormous. If someones address is denormalized into 1000 contact records, then when the user updates their address the system has to go out to all of the contact records and update them as well. And this gets multiplied by every complex relationship that exists in the data. And redundant fields can increase data size exponentially.
Regardless, denormalization is only one option. It just seems that Google should publish the guidelines for how to manage complex data relationships with clear guidance on advantages and disadvantages for each strategy. It's an important architectural consideration and we are currently left to hunt and peck around for what is even available let alone best practice for a given set of system requirements. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/k9TWBll6XqwJ. 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.
