Hi,
I got a question regarding how to implement a specific problem (and
make it scale without reaching any hard quotas implied by GAE).
my problem: Think of a Google Reader like application - there must be
a mechanism that stores items read by a user.
I would implement it as:
- object USER with an ID (say, Long)
- object ITEM with Set<Long> idsOfUserThatReadThatItem.
then I have millions of USER objects and millions of ITEM objects, and
every time a user read an ITEM I would add the id to the set of the
respective ITEM.
I could also easily query the ITEMS read by a user using JDO syntax
and setFilter("idsOfUserThatReadThatArticle==id_user").
On the other hand I know that there are hard quotas such as the 1MB
quota on entities. Does this affect the Set<Long>
idsOfUserThatReadThatItem saved along with my object ITEM?
Because then I could only save a very limited amount of Users that
read an ITEM (I would guess 200 Longs in a Set).
Thanks!
Raphael
--~--~---------~--~----~------------~-------~--~----~
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 [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-java?hl=en
-~----------~----~----~----~------~----~------~--~---
