D
dbeavon
Guest
>> We have been using Redis as a fast in-memory cache database I have only done a little bit of reading about redis. The challenge I often face is when I'm working with lots of data (eg. 100,000 rows in a handful of tables.) Progress would have to do substantial work when it comes to the serialization or marshalling of that data. I was hoping for a solution where 100,000 rows (and related indexes) would be instantly available for an ABL session to start using (as TT/DS data). It would be nice if the *only* work that needed to be done was to simply "attach" a client-session to the local data. If we could "detach" from a client session's TT data and make a copy of the underlying file(s), then I would certainly consider storing that in redis for other ABL client sessions to use in the future - once they are ready to "attach" to it.
Continue reading...
Continue reading...