While reading Adam's proposal I came to realize that: we don't have to
calculate winning revision at read time.
Since FDB's transactions are atomic we can calculate it when we write. This
means we can just write latest values into separate range. This makes lookup of
latest version fast.
Hi everyone,
One thing that has plagued the CouchDB project for a while is the
introduction of new features without much discussion prior to the
feature landing.
To put all the cards on the table: it is good that IBM/Cloudant have
been benevolent and have contributed significant new
Solution (2) appeals to me for its conceptual simplicity -- and having a
stateless CouchDB layer I feel is super important in simplifying overall
CouchDB deployment going forward.
--
Mike.
On Mon, 4 Feb 2019, at 20:11, Adam Kocoloski wrote:
> Probably good to take a quick step back and note
