nosql and document db are all the rage right now, but I am stumped as to when I would really need one. but then it hit me. web + service bus + doc db makes pretty good sense. after all if a web application consumes a message it doesn't have access to the asp.net stack, so you need to store the results of that message somewhere. this leaves 2 obvious choices: in-memory and serialized to an RDBMS database. memory only works if you don't care about loosing a message. a RDBMS seems like overkill or just the wrong fit for this sort of thing.
This leaves 2 other options (1) PHT and (2) RavenDB. both make sense and depending on your needs one may be a better fit than the other. However the idea of using linq to get the results is much more appealing than PHT. yes, I could abstract PHT behind some interface. But if Raven uses linq directly that seems to make much more sense. plus Raven offers map/reduce and aggregation-like operations which can open more possibilities. This leads to another question though... what is the difference between a Document DB and a Persistant Hashtable? or what is the purpose of PHT vs Raven? -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
