Reputation
14,927
Top tag
Next privilege 15,000 Rep.
Protect questions
Badges
5 27 70
Newest
 Nice Answer
Impact
~614k people reached

23h
revised Approaches to Modeling a Graph Database over the Google App Engine Datastore?
deleted 220 characters in body
23h
revised Approaches to Modeling a Graph Database over the Google App Engine Datastore?
deleted 220 characters in body
23h
comment Approaches to Modeling a Graph Database over the Google App Engine Datastore?
the parent is supposed to own the entity so that is how it is designed, that relationship will never change. A graph is queried the same way regardless unlike a SQL database where you are concerned with the queries. There is only one class of query in a graph database. All of the X where Y has a Z relationship, and then they get nested and or filtered. The DataStore is a raw Key/Value store, it is fast for individual key lookups and ancestry lookups where the parent is known, it actually groups all those entities locally and indexes them as such.
23h
revised Approaches to Modeling a Graph Database over the Google App Engine Datastore?
added 617 characters in body
1d
comment Is there empirical evidence supporting Brook's Law (or a modification of it)?
9 women can not make a baby in a month. That is empirical evidence.
1d
asked Approaches to Modeling a Graph Database over the Google App Engine Datastore?
1d
answered How can I model this scenario in a graph database?
Aug
20
revised Write a directory structure (pseudo code)
edited body
Jun
10
revised Member: Use unique IDs vs domain object
added 1 character in body
Jun
6
revised Member: Use unique IDs vs domain object
added 168 characters in body
Jun
6
comment Member: Use unique IDs vs domain object
if C-> A -> B -> A and B is put into a Collection then A and all its children are still reachable, these things are not completely obvious and can lead to subtle leaks. GC is the least of the problems, serialization and deserialization of the graph is a nightmare of complexity.
Jun
6
revised Member: Use unique IDs vs domain object
added 30 characters in body
Jun
6
comment Member: Use unique IDs vs domain object
I added an explicit explanation.
Jun
6
revised Member: Use unique IDs vs domain object
added 727 characters in body
Jun
6
answered Member: Use unique IDs vs domain object
Jun
1
awarded  Nice Answer
May
28
revised Semantically more appropriate package name than `util` for the following things?
added 6 characters in body
May
27
awarded  Nice Question
May
27
revised Avoiding lot of roles implementation in same object
deleted 425 characters in body
May
27
comment Avoiding lot of roles implementation in same object
@rdllopes - your question is an X-Y Problem, where Y is this Adapter Pattern solution and you are asking if it is a good design, when you need to be asking what others have done, it is not this Adapter Pattern approach.