Per-Entity Metadata Working Group

["Walter Forbes Hoehn (wassa)" <>]

So far, I’ve only heard option “a” discussed. What this buys you is simply a 
cache that spans restarts for the entities already “seen” by the node.

-WFH


> On Aug 11, 2016, at 2:51 PM, Scott Koranda 
> <>
>  wrote:
> 
>> On Thu, Aug 11, 2016 at 2:46 PM, Walter Forbes Hoehn (wassa)
>> <>
>>  wrote:
>>> … design highest possible availability into the server,
>>> but hedge with client features.
>> 
> 
> Please forgive me for being pedantic:
> 
> Scott C, do you envision for "caching"
> 
> a) writing to disk the metadata for an entity each time it has
> been fetched successfully to be used to accomplish a SAML flow
> 
> or
> 
> b) periodically downloading an aggregate that contains all of
> the entities (since we expect aggregates to stay around for
> some time) and writing it to the side on disk but not using it
> except when detecting that MDQ queries are failing (hence not
> having to take up memory when not necessary).
> 
> or
> 
> c) some combination of (a) and (b)
> 
> or
> 
> d) other
> 
> Thanks,
> 
> Scott K