Failures and antipatterns · Intermediate
Connection-pool leaks
Distinguish database activity from pool ownership and verify resource return across success, exception and cancellation paths.
Read and check your understanding →LAVACS KNOWLEDGE
Identify failure mechanisms from symptoms and choose remedies with their trade-offs in mind.
35 articles · page 2 of 2
Failures and antipatterns · Intermediate
Distinguish database activity from pool ownership and verify resource return across success, exception and cancellation paths.
Read and check your understanding →Failures and antipatterns · Intermediate
Trace references that survive deallocation and repair ownership using the allocation, release and later-access sequence.
Read and check your understanding →Failures and antipatterns · Intermediate
Compare input length with allocation bounds in matching units and investigate the arithmetic and ownership behind out-of-bounds writes.
Read and check your understanding →Failures and antipatterns · Intermediate
Distinguish stack exhaustion from buffer corruption and investigate recursion depth, frame size and runtime limits together.
Read and check your understanding →Failures and antipatterns · Intermediate
Trace competing release responsibilities for one allocation and align ownership transfer with a single cleanup contract.
Read and check your understanding →Failures and antipatterns · Intermediate
Trace changes between validation and use, and choose object-bound operations or conditional updates at the required boundary.
Read and check your understanding →Failures and antipatterns · Intermediate
Investigate competing writers by separating quorum decisions, leadership terms and fencing of external resources.
Read and check your understanding →Failures and antipatterns · Intermediate
Trace stale values after source updates and define freshness using invalidation, refills, versions and authorization boundaries.
Read and check your understanding →Failures and antipatterns · Intermediate
Separate message redelivery from business effects and design deduplication around the point where acknowledgements can be lost.
Read and check your understanding →Failures and antipatterns · Intermediate
Trace partial success across independent services and design recovery around actual atomicity boundaries and uncertain outcomes.
Read and check your understanding →Failures and antipatterns · Intermediate
Trace how one slowdown spreads through retries, queues and shifted traffic, then protect useful work with admission and deadline policies.
Read and check your understanding →Use the knowledge map to find prerequisites, or follow a learning path in order.