knobit.org

C1 (2 points)

edu:Question

https://knobit.org/id/task/dii-flow-resilience/C1

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/dii-flow-resilience/C1
rdfs:labelC1 (2 points) en
schema:hasPartdii-flow-resilience C1a: PF-01 nightly batch reported as too slow for real-time fraud scoring
schema:hasPartdii-flow-resilience C1b: PF-01 given a streaming or log-based CDC pattern with latency in seconds
schema:identifierC1
schema:position1
schema:textPattern against the consumer's need, 1 each. (a) PF-01 is reported as too slow for its consumer: a nightly batch of the previous day feeds a fraud score that must be computed within the 10-second SCT Inst limit on the debtor's payments of the last minutes, so the feature is up to a day stale exactly when fraud happens. (b) PF-01 gets a pattern that meets the need: streaming from the existing pay-inst topic (publish-subscribe) or log-based CDC on pay.instant_payment, with a latency of seconds - not 'run the batch hourly' or any schedule of minutes or more. en

Used by

has questionPayments and financial-crime flows - dead letters, replay and latency, with the reasons behind resilient flows (integration pattern skills)
schema:isPartOfdii-flow-resilience C1a: PF-01 nightly batch reported as too slow for real-time fraud scoring
schema:isPartOfdii-flow-resilience C1b: PF-01 given a streaming or log-based CDC pattern with latency in seconds