Thanks - Records have no hard size limit - but are limited to the maximum size of your cache entry or database document. The tcp connection can send a single re

Thanks - Records have no hard size limit - but are limited to the maximum size of your cache entry or database document. The tcp connection can send a single record update over multiple packets. - Records already have a version that's incremented with every change and also persisted as part of the record's meta-data. Currently deepstream uses a simple first-wins strategy and subsequent updates for the same version number get rejected. However configurable merge strategies are in planning as part of a "record-options" setting. - Currently data has to be explicitly deleted from the cache.