Queries repeatedly read the same keys, and you need microsecond access. What fits?
Why C is the answer
Memorystore
Memorystore is the in-memory store.
In detail
- Memorystore gives microsecond access to cached data.
- Memory is costly, so cache what is hot.
Use case
An illustrative scenario, not a real incident.
An app reads the same product keys constantly, and Memorystore answers in microseconds.
See it in different ways
flowchart TD
A{"Access pattern"} -->|"Analytics in SQL"| B["BigQuery"]
A -->|"Huge key lookups"| C["Bigtable"]
A -->|"Global relational consistency"| D["Spanner"]
A -->|"Regional relational app"| E["Cloud SQL or AlloyDB"]
A -->|"Objects and files"| F["Cloud Storage"]
A -->|"In-memory cache"| G["Memorystore"]mindmap
root((Stores))
BigQuery
Analytics
Bigtable
Key lookups at scale
Spanner
Global relational
AlloyDB
PostgreSQL
Firestore
Mobile documents
Memorystore
Microsecond cache
Cloud Storage
ObjectssequenceDiagram participant P0 as App participant P1 as Memorystore participant P2 as Database P0->>P1: Get key P1-->>P0: Hit P0->>P2: Read on a miss
Key point: Memorystore is in-memory.
Why the other options are wrong
- A. BigQuery
- BigQuery is for analytics.
- B. Transfer Appliance
- An appliance moves data offline.
- D. Cloud Storage Archive
- Archive storage is slow.