Access pattern
An access pattern is the characteristic or recurring way a system accesses data or resources, including reading, writing, or querying them.
C++ Concurrency in Action, Second Edition
A data access pattern is the way a computation reads or writes locations in memory over time.
- How it is used
- Guides how concurrent work is divided and when workers should stop accessing data.
- How deep it goes
- Works through matrix thread assignments, then extends the reasoning to trees, mutex placement, and parallel search.
- Examples
- Uses row-contiguous matrix multiplication, a padded mutex layout, and parallel std::find with an atomic completion flag.
- What you can do after
- Diagnose/debug with it by identifying false-sharing risks in work assignments and unnecessary work in parallel searches.
Read how C++ Concurrency in Action, Second Edition explains access pattern →
ScyllaDB in Action
A query pattern is a recurring form of data retrieval or mutation that an application must support.
- How it is used
- Guides data modeling and query design by expressing how an application repeatedly retrieves or mutates its data.
- How deep it goes
- Explains partition-key routing, cross-partition scans, and performance consequences through concrete CQL queries.
- Examples
- Uses restaurant-review lookups by restaurant, ordered_at, or both, including CQL output and a filtering warning.
- What you can do after
- Apply it via CQL by structuring data and queries around partition-key access instead of broad partition scans.
PostgreSQL Mistakes and How to Avoid Them
A usage pattern is a recurring way in which a database system or feature is configured or used.
- How it is used
- Uses recurring database behavior to identify inefficiencies, anomalies, bottlenecks, and opportunities for preventive improvement.
- How deep it goes
- Connects pattern recognition to review, analysis, staging tests, monitoring, and planned intervention, without prescribing detailed diagnostic commands.
- Examples
- Uses table bloat, billion-row growth, partitioning, cloud costs, connection limits, long transactions, autovacuum, locks, and indexes.
- What you can do after
- Diagnose emerging PostgreSQL problems and plan, test, monitor, and roll out corrective changes before they escalate.
Read how PostgreSQL Mistakes and How to Avoid Them explains access pattern →
Related concepts
- partitioning keyuses · A partitioning key is a value or attribute used to determine which partition stores or receives a record or data item.
- task-based work divisionused by · Assignment of different tasks or responsibilities to different threads rather than giving each thread a portion of the same data.
- performancecontrasts with · Performance is the measurable effectiveness or operational behavior of a system under specified conditions, assessed through relevant qualities such as task results, speed, responsiveness, throughput, or resource use.
- prefetchused by · Prefetching is the proactive retrieval or preparation of anticipated data or resources before they are needed.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.