Search the practice set

126 questions, 454 terms and 400 topics in 20 areas.

12 results for “Pattern Recognition”

Terminology · 11
term

Pattern Recognition

Recognising that a novel-looking problem is an instance of one you have seen before, and knowing which parts of the previous solution transfer.

Meta-Skills
term

Outbox Pattern

Writing an outgoing message into a table in the same transaction as the business change, and relaying it to the broker separately, so the two cannot diverge.

Architecture Patterns
term

Architecture Style

A named, coarse-grained way of organising a whole system, as distinct from a pattern that solves one recurring problem inside it.

Architecture Fundamentals
term

Caching Strategy

The chosen pattern for how a cache is populated, read and invalidated — cache-aside, read-through, write-through or write-behind.

Performance & Capacity
term

Data Lakehouse

A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.

Data Architecture
term

Fallback Strategy

What a caller does instead when a circuit breaker is open — the part of the pattern that determines whether failing fast helps anyone.

Circuit Breakers
term

Hot, Warm and Cold Data

Classifying data by how frequently and how urgently it is accessed, so each tier can be stored on media priced for that access pattern.

Data Lifecycle & Retention
term

Lock Lease Expiry

The timeout on a distributed lock that prevents a crashed holder deadlocking the system — and the source of the pattern's hardest failure mode.

Distributed Locking
term

Publish/Subscribe

A messaging pattern where each published message is delivered to every interested subscriber, rather than to one competing worker.

Architecture Patterns
term

Strangler Fig

Replacing a legacy system incrementally by routing individual capabilities to new implementations behind a facade, until nothing routes to the old system.

Architecture Patterns
term

Try-Confirm-Cancel

A three-phase distributed transaction where each participant first reserves resources, and a coordinator then confirms or cancels all reservations.

Distributed Transactions