liveBook · Manning

Access pattern

As explained in Grokking Software Architecture

A repeatable way an application reads from and writes to its storage, including query shapes and read-to-write ratios.

An access pattern is a repeatable way an application reads from or writes to storage. A schema describes what data looks like; access patterns describe how it moves. Choosing a database with those patterns in mind is more useful than shopping by feature list alone. section 8.2.1

Map the traffic your application actually expects:

  • What shapes do queries take, and how do they find data? section 8.2.1
  • How many reads occur compared with writes? How large are the payloads? section 8.2.1
  • How much latency can the application tolerate? section 8.2.1

Orders and payments

A request for active orders placed by customers in Asia over the past 30 days, alongside their payment history, crosses several domains. A relational database can answer this kind of complex request using SQL joins. section 8.2.1

Start with a relational database for typical business data, but let evidence about the actual workload guide the choice—not hunches. section 8.2.1

How Grokking Software Architecture covers it

How deep it goes
Defines access patterns and identifies query shapes, traffic ratios, payload sizes, latency tolerance, and lookup pathways as factors to examine.
Examples
Illustrates a cross-domain query for active Asian customer orders and their payment history.
What you can do after
Evaluate whether complex, cross-domain queries support choosing a relational database.
How it connects
Connects access patterns with schemas, relational databases, and SQL joins.

Also explained in

Compare how 5 books explain access pattern →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.