Closed slawr closed 2 months ago
@93arnaldo has been making progress on the Realm backend to WAII. Assigning @93arnaldo and @humza-akhtar to the task.
@93arnaldo has a C++ process that can act as a front end to a Realm store. In last weeks call he was considering how best to integrate into the VISS Data Server
There has been discussion in the Data Architecture calls about the paradigm differences between key/value VSS data pairs in a timeseries and the possibly complex and app specific structures of a "document" data model as employed in a NoSQL DB like Realm. A related question therefore is whether it makes sense to create an interface layer for Realm as a backend to the key/value expected by a VISS Data Server, or to instead use it purely in cases where the paradigm makes sense in related applications.
@93arnaldo @humza-akhtar should we consider changing this issue from the current (narrow) specific description to something more speculative to be answered related to the relationship between NoSQL documents and key/value pairs, with Realm as an example?
I would very much like to keep MongoDB as part of the discussion. Feel free to respec this as you see fit and we can discuss further. Related to this is how we represent this in sessions at the AMM.
Upstream WAII project was renamed VISSR as part of its move from W3C to COVESA. Renamed title and description
Moving this to backlog whilst we decide what to do regarding Realm and VISS. Current focus of work on Realm is in knowledge layer connector #44.
Agreed in 29th May Data Arch meeting
No update on this for a long time and as mentioned in the previous comment work on Realm is currently focused in the knowledge layer connector. So closing this. Can be reopened in future if it makes sense.
Extend VISSR to support the MongoDB Realm embedded DB as a data store backend.
Work breakdown: