[Ndn-interest] Repo vs aggregation queries

Ernest McCracken emccrckn at gmail.com
Fri Jul 19 10:51:57 PDT 2019


>
>
>
>
>
> From this discussion it almost seems like these repos should act as NDN
>> adapters to existing storage and grid storage solutions providing a basic
>> but extensible naming schema.  Of course developing that naming schema and
>> mapping can be complex.  Lots of new storage solutions like redis.io are
>> making querying language simpler and are used in enterprise systems today.
>> Redis is used extensively by Discord for instance.
>>
>
> This describes an NDN frontend of a database, where the data schema is
> defined per application. I can certainly have a BLOB column that stores the
> original Data packets coming from the sensor, in addition to individual
> columns of temperature, humidity, etc, so that it can serve both original
> Data packets and aggregation queries.
> However, this would not be a repo, because a repo is supposedly general
> purpose and can store data from any application (as permitted by trust
> policy).
>
> I agree with the notion that this would be a front end for a datastore and
> while redis (an inmemory data structure store) and noSQL db's require
> little to no schema they do require the application to conform to those
> structures. Is a requirement of repo to store application data in its
> original format?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20190719/393cf8f9/attachment-0001.html>


More information about the Ndn-interest mailing list