PCDOE-1 Quick, GCP Professional Cloud DevOps Engineer - SLIs, Quality, Availability, Latency

แชร์
ฝัง
  • เผยแพร่เมื่อ 30 พ.ย. 2024

ความคิดเห็น • 4

  • @Murlik1604
    @Murlik1604 3 ปีที่แล้ว +3

    Hi Satish,
    Still seem to be conflicted with option B :), as my thought process was the availability of the application and DB is more under the control of the infrastructure with load balancing, failover options but the latency of the application will be be influenced by external factors like too many requests on christmas day which the stake holder might be interested in measuring and controlling. If the web application and DB is not able handle the requests in timely manner or the analysis job throughput is not good , it might impact the end reports being stale.
    Option C- for Batch Job freshness, Is there a direct quality measure available which can be leveraged ?

    • @AwesomeGCP
      @AwesomeGCP  3 ปีที่แล้ว +4

      The batch jobs for the report generation are not run immediately, and therefore the latency wouldn't impact the report generation much. Also do note that latency for these online systems is usually in seconds, not hours or even minutes. The impact of a little latency is typically ignorable in such situations like report generation.

    • @pawanphalak5072
      @pawanphalak5072 3 ปีที่แล้ว +2

      @@AwesomeGCP Great points, but Is freshness a standard and quantitative measure?(seems similar to quality)

  • @dubemahendra
    @dubemahendra 3 ปีที่แล้ว +1

    Very Good Explanation...thanks