New answers tagged

0

I use following pattern for key and values that should be indexed in key: { "id":"ObjectId", "key":"error1" "values":[{"languages":"en", "test":"Error Message 1"}, {"languages":"fa", "test":"متن خطای شماره 1"}] } } object = coleccion.find({"key": "error1"}); view this link Model One-to-Many Relationships with Embedded Documents! I Reshare ...


1

Yes, what you propose is a bad practice. All your read operations are now potentially write operations as well. This means that they will have the same concurrency implications as write operations and you will have to deal with parallel and potentially conflicting updates of the same document. A better solution is to not store attributes that can be ...


1

In an event driven structure your transaction completes when you mark the event completed; preventing its being re-executed. ie deleting it from the queue or whatever retry system you have in place. So regardless of your db tech the process is Pull message do calculations write state post next message(s) in train delete message If you fail before write ...


Top 50 recent answers are included