Thanks for providing more of a use case. You mention wanting to determine if 2 entity kinds belong in the same group. From your 3 requirements, it seems like there are several entity kinds: *account balance*, *bank*, *member*, *money transfer*. I am unclear on how entities of these kinds relate to another and what dependencies they have.
- How are entities of each of these kinds related to one another (hierarchy and such)? - How often do entities of each kind get changed? - Which CRUD operations with each entity kind require strong consistency? Knowing the above may help with providing more specific architecture suggestions regarding entity groups, transactions and the use of ancestor queries. On Tuesday, October 4, 2016 at 8:23:24 PM UTC-4, Paul Mazzuca wrote: > > Is there any reason to use an Entity Group in Google Datastore other than > for enabling transactions? > > For example, does having entities in the same entity group speed up > queries? The situation that I run into often is whether to have X be a > parent to Y or have X be a property of Y. Both cases allow for Y to be > queried given X, but when transactions aren't needed perhaps the entity > group is not necessary. I guess another way of stating the question is > whether or not ancestor queries provide speed up over property based > queries without ancestors? > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/d9fe54cd-db7b-41f3-bc5a-558884feb9d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
