Seems pretty useful actually. Can anyone with a relevant background comment on when this would be a bad idea to use?
Seems pretty useful actually. Can anyone with a relevant background comment on when this would be a bad idea to use?
But in some cases you don't have that same constraint. For example, databases that store logs (Elastic, Splunk, etc) might have many readers and writers, including humans.
In that case enforced immutability might be a nice property to have. Attackers who get access to your Splunk/ES cluster certainly will have fun with it.
We evaluated AWS QLDB for these things in our application as a financial ledger and were impressed at their progress with a novel data store. They invented some of the tech in house for this product instead of grabbing an off the shelf open product. Lockin would be a downside here.
Immudb looks promising because it's not locked to a cloud host.
not an "all or nothing" question.. for example, a fast-enough "return the most recent in a time series" is not exactly time-series, but solves many use cases