Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
21 results for “Sync & Conflict Resolution”
Last Writer Wins
Resolving a conflict by keeping the version with the later timestamp — simple, deterministic, and it silently discards the other change.
DNS Resolution Chain
The sequence of lookups from browser cache through OS cache, recursive resolver, root, TLD and authoritative server that turns a name into an address.
Immutable Store Erasure Conflict
The direct contradiction between architectures designed never to forget and obligations requiring data to be removed, which must be resolved in the design rather than in policy.
N+1 Resolution
The default GraphQL execution behaviour in which each field resolver runs per item, producing one query per row instead of one query per request.
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
DNS
The distributed directory that resolves names to addresses, and a surprisingly load-bearing part of most architectures.
Governed Self-Service
Letting anyone analyse anything while constraining what may be treated as authoritative, which resolves the apparent conflict between speed and consistency.
Narrative Arc
Structuring a technical presentation as a problem, tension and resolution rather than as an ordered dump of findings.
Optimistic Concurrency Control
Allowing concurrent work without locks and detecting conflict at write time by checking that the underlying version has not changed.
Request-Reply and Fire-and-Forget
The two interaction shapes available between components, differing in whether the caller waits for a result and therefore in whether availability compounds.
Term Definition Ownership
Assigning one accountable owner per business term, so that a disagreement about meaning has a route to resolution rather than a standing argument.
Version Vector
A per-replica counter set that lets a system tell whether one version causally descends from another or whether the two are genuinely concurrent.
A field application has been live for three months and support reports that engineers occasionally lose completed job reports. What do you investigate?
Suspect last writer wins on a record level merge The pattern fits exactly. Two writers touch the same record — the engineer's device and the office, or two devi
You are designing a field-service application for engineers who work in basements and rural sites with no reliable connectivity. What is the architecture, and what are the decisions that will bite later?
The shape: local first, with the server as an eventual replica Connectivity is an optimisation, not a precondition. The application writes to a local store, ren
An order API calls six services synchronously and takes 3 seconds at p95, failing whenever any dependency is degraded. Redesign it.
Diagnose with arithmetic Six synchronous dependencies at 99.9% each give 99.4% — roughly four hours a month, from components that are individually fine. And lat
When should a service call another synchronously, and when should it publish an event instead? Give me the deciding test, not a preference.
The deciding test Does this user action succeed or fail based on this callee's response? If yes, the call is synchronous, because you need the answer to decide.
Sync & Conflict Resolution
Two devices that both changed the same record while neither could see the other.
Sync vs Async
Whether the caller's outcome depends on the callee's response.
DNS
Resolution, TTL behaviour, traffic steering and failover latency.
GraphQL
Client-specified queries, N+1 resolution and query-cost control.
Trade-off Analysis Methods
ATAM, scenarios, and naming the points where qualities conflict.