nosql

I've looked at MongoDB/norm (but want a general document-oriented store answer). It seems really nice to work with and I'm interested in knowing when it should be used instead of RDBMS+ORM? What should i use for for instance: Stackoverflow similiar sites Social communities forums (I posted another more general question but it got a splendid answer that might be interesting for others, hence the new question) All of the examples you mentioned can be built using a document store. Whether you should use it, depends on the exact requirements. If you're dealing with a social community that supports

I have some question about handling message that failed to response success, but success commit to database. The design that I think is for guarantee processing message once. Following sequences are step for handling. Question is included on statements with ★ 1) Fetch message from Message Queue -> When failed after this, MQ will timeout & retry 2) Cache.SetIfNotExist(MessageId, MyId, Timeout) ProcessingTime < Cache.Timeout < MQ.Timeout * This make ownership for message -> When failed after this, Cache will timeout and MQ will timeout & retry 3) Processing Data include read storage * All of

We've been discussing design of a data warehouse strategy within our group for meeting testing, reproducibility, and data syncing requirements. One of the suggested ideas is to adapt a NoSQL approach using an existing tool rather than try to re-implement a whole lot of the same on a file system. I don't know if a NoSQL approach is even the best approach to what we're trying to accomplish but perhaps if I describe what we need/want you all can help. Most of our files are large, 50+ Gig in size, held in a proprietary, third-party format. We need to be able to access each file by a name/date