A single MongoDB document as internal database/storage

[zestsystem]

Based on the CRUDInterface implementation of Json database example, I made a CRUDInterface that takes in a single "tournament" mongo document as the internal database/storage. And it "works" but Im not sure if this is intended use...

I like that since all updates are done in one document, changes in multiple fields are atomic and requires no more than one database write.

What do you think are problems with this approach if at all?

[Drarig29]

I started a draft PR 3 months ago to support IDs as strings (as primary IDs are in mongodb) but you can do without too!

I'm not sure how your custom CRUD interface works, but you could also use brackets-memory-db instead of implementing your own CRUD interface, just like brackets-viewer.js does in the demo.

You would set the InMemoryDatabase data to be your fetched document. Do mutations on the tournament with the manager and then push the mutated data back into mongodb.

This means that you wouldn't need to perform multiple "intra-document" mongodb requests: just a fetch and a push.

And you can almost view this as a "transaction" because if the manager throws an error during the process, your tournament data will stay untouched.

[zestsystem]

Yup that's what I have right now with the mongodb crud interface thing . It just mutates the document itself and only saves after all the updates and works like a "transaction" , which I found was neat. Using mongodb felt hacky just bc the storage example didn't explicitly have mongodb listed. I will take a look at the bracket-memory-db and see if that should work better. Thank you for the help :)