Hi.
This is a great project. Thanks for putting it together.
MongoDB is performing pretty poorly on most of the benchmark tests provided. Despite this we're still considering it as the right solution, partly due to this one killer feature, which is perfect for our use case:
All of the other datastores that are being benchmarked would require the client to retrieve the document, update it and reinsert it, which I estimate would be will be much slower than the single 'update' operation provided by MongoDB above. This would be particular true for large, highly nested documents.
It would be really interesting and useful to add a benchmark test for this!
Hi. This is a great project. Thanks for putting it together.
MongoDB is performing pretty poorly on most of the benchmark tests provided. Despite this we're still considering it as the right solution, partly due to this one killer feature, which is perfect for our use case:
https://docs.mongodb.com/v3.0/reference/operator/update/set/#set-fields-in-embedded-documents
All of the other datastores that are being benchmarked would require the client to retrieve the document, update it and reinsert it, which I estimate would be will be much slower than the single 'update' operation provided by MongoDB above. This would be particular true for large, highly nested documents.
It would be really interesting and useful to add a benchmark test for this!