The Record Layer paper says the following:
To avoid exposing FoundationDB’s limits on key and value sizes to clients, the Record Layer splits large records across a set of contiguous keys and splices them back together when deserializing split records. A special type of split, immediately preceding each record, holds the commit version of the record’s last modification; it is returned with the record on every read.
Seems like a developer doen’t have to worry about key-val sizes with Record Layer, or is there any catch here?
Does it mean that the total data size in a transaction (<= 10 MB) is also not an issue here?