Design patterns and optimization · Intermediate
Idempotent requests: retry without duplicating effects
Use a lost order response to reason about idempotency keys, atomic records, and the retention window.
Read and check your understanding →LAVACS KNOWLEDGE
Compare design approaches through their motivating problems, implementation examples, and trade-offs.
30 articles · page 1 of 2
Design patterns and optimization · Intermediate
Use a lost order response to reason about idempotency keys, atomic records, and the retention window.
Read and check your understanding →Design patterns and optimization · Intermediate
Combine capped waiting, randomization, an overall deadline, and a contract for retryable operations. Work through concrete cases and separate mathematical assumptions from implementation checks.
Read and check your understanding →Design patterns and optimization · Intermediate
Make waiting, rejection, and load reduction explicit when arrivals exceed processing capacity. Work through concrete cases and separate mathematical assumptions from implementation checks.
Read and check your understanding →Design patterns and optimization · Intermediate
Trace read-through filling, write invalidation, races, and expiration without assuming the cache is always current.
Read and check your understanding →Design patterns and optimization · Intermediate
Reason about amortized overhead, batch formation delay, size limits, deadlines, and failure boundaries.
Read and check your understanding →Design patterns and optimization · Intermediate
Design cache keys, generations and publication order so that a refresh cannot silently mix incompatible versions.
Read and check your understanding →Design patterns and optimization · Intermediate
Centralize cache-miss loading while making concurrency, negative results and origin failures explicit.
Read and check your understanding →Design patterns and optimization · Intermediate
Define what a synchronous cached write acknowledges and reason about partial failure across cache and origin.
Read and check your understanding →Design patterns and optimization · Intermediate
Separate acknowledgement from persistence and design the dirty queue, retries, ordering and recovery explicitly.
Read and check your understanding →Design patterns and optimization · Intermediate
Separate freshness lifetime from a bounded stale window and understand when background revalidation is allowed.
Read and check your understanding →Design patterns and optimization · Intermediate
Protect a constrained resource before work begins by defining concurrency limits, queueing, rejection and deadlines.
Read and check your understanding →Design patterns and optimization · Intermediate
Balance uneven parallel tasks by letting idle workers obtain work from other workers, while accounting for overhead and locality.
Read and check your understanding →Design patterns and optimization · Intermediate
Keep readers on immutable snapshots while separating copying, publication and mutable element ownership.
Read and check your understanding →Design patterns and optimization · Intermediate
Choose AoS, SoA or blocked layouts from the fields and access sequence a computation actually uses.
Read and check your understanding →Design patterns and optimization · Intermediate
Process bounded batches to amortize execution overhead while distinguishing vectorized query execution from hardware SIMD.
Read and check your understanding →Design patterns and optimization · Intermediate
Commit business updates and send intent locally, then trace crashes, duplicates, ordering and backlog to identify the guarantee boundary.
Read and check your understanding →Design patterns and optimization · Intermediate
Use concurrency, bounded queues, deadlines and priorities to reject excess work while preserving result semantics and recovery.
Read and check your understanding →Design patterns and optimization · Intermediate
Compare a shared pool with reserved dependency pools, tracing stalled work, idle capacity, parent waits and release paths.
Read and check your understanding →Design patterns and optimization · Intermediate
Trace closed, open and half-open states while separating failure windows, bounded probes, local refusals and fallback semantics.
Read and check your understanding →Design patterns and optimization · Intermediate
Use original requests, extra-attempt allowances and multilayer amplification to distinguish count limits, retry timing and idempotency.
Read and check your understanding →Design patterns and optimization · Intermediate
Allocate a 300 ms end-to-end budget across services and distinguish clocks, retries, cancellation and already committed effects.
Read and check your understanding →Design patterns and optimization · Intermediate
Commit received identity with its business update, then reason about concurrency, payload conflicts, retention and projection rebuild scope.
Read and check your understanding →Design patterns and optimization · Intermediate
Trace reservation, payment and cancellation to specify compensation retries, unknown outcomes, local invariants and recovery ownership.
Read and check your understanding →Design patterns and optimization · Intermediate
Use an order and lagging list projection to reason about authority, replay, progress, rebuilding and independence from event sourcing.
Read and check your understanding →Use the knowledge map to find prerequisites, or follow a learning path in order.