knobit.org

I1 (2 points)

edu:Question

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

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
rdfs:labelI1 (2 points) en
schema:hasPartdii-flow-resilience I1a: replay from the last committed offset made safe by an idempotent receiver, rejects to a dead letter channel
schema:hasPartdii-flow-resilience I1b: Kafka orders within a partition only; per-customer order by re-keying or a resequencer
schema:identifierI1
schema:position4
schema:textWritten answers, 1 each. (a) Q-1 explains that delivery is at least once, so a replay from the last committed offset redelivers events already applied; the upsert on customer_id (guarded by log position) makes reapplying them harmless - an idempotent receiver - and an event the consumer cannot apply goes to the dead-letter topic, whose owner reviews it and republishes it after the fix. (b) Q-2 explains that Kafka orders only within a partition: card-txn keyed by card_id gives order per card, none across a customer's cards in different partitions; per-customer order needs re-keying by customer_id or a resequencer by customer_id on event_time. 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 I1a: replay from the last committed offset made safe by an idempotent receiver, rejects to a dead letter channel
schema:isPartOfdii-flow-resilience I1b: Kafka orders within a partition only; per-customer order by re-keying or a resequencer