Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] implementing a cache on the client

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] implementing a cache on the client


Chronological Thread 
  • From: Chris Phillips <>
  • To: "" <>
  • Subject: Re: [Per-Entity] implementing a cache on the client
  • Date: Thu, 4 Aug 2016 14:51:54 +0000
  • Accept-language: en-US

Yes. We are in general alignment. I won't go as many '>' as you however.
I'm reluctant to sacrifice instrumentation at all costs for
reliability/performance, but will definitely favour
reliability/performance. For the report, I think it's about what's
possible and at what estimated cost for an implementation.


Do you go to a 'restaurant' for a good meal, a fast meal, or an economical
meal?

Does one implement MDQ for reliability/performance, with visibility, or
cost effectiveness?


Either question is a pick 2 from the 3 options unless you aim for 'what's
sufficient from each?'

C

On 2016-08-04, 10:36 AM, "Cantor, Scott"
<>
wrote:

>This is why I'm not so sure of the cost involved in achieving adequate
>reliability, and adding the requirement to have total visibility on top
>of that may create a basic conflict. I think reliability/performance >>>
>visibility.




Archive powered by MHonArc 2.6.19.

Top of Page