It depends on the size of your user-base / complexity of your application's chat system.
If you have millions of users having millions of chats this wouldn't be so much fun. Otherwise it should work. You can always hide the implementation behind an API in your app and then be able to change how you actually store the chats later. You could implement the chats just as a message nodes that are connected to the chat, and the author. Properties would be text and timestamp. Those nodes could also additionally be linked from HEAD to LAST to traverse the chat. There could be a special relationship from the "chat"-ndoe to the HEAD of the conversation. Another idea is to have the chat message just on the relationship between author and chat (same properties as above). You could use a timeline index for accessing them in the right order. You could also have a look at the neo4j-collections API that Niels implements and use just a linked list of that API. Cheers Michael Am 26.07.2011 um 00:48 schrieb noppanit: > I'm implementing chat feature in my application, but the main features I'm > still using neo4j for relationships. BTW, I'm not sure how am I going to > implement chat log in neo4j, because it's not about relationships. Should I > just go for mongodb or other nosql database in this particular case? > > Thank you. > > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-and-chat-log-structure-tp3198962p3198962.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
