An app needs PostgreSQL compatibility with high performance. Which service fits?
Why A is the answer
AlloyDB
AlloyDB is the PostgreSQL-compatible database.
In detail
- AlloyDB is PostgreSQL compatible, with high performance.
- Existing clients keep working.
Use case
An illustrative scenario, not a real incident.
An app built on PostgreSQL needs more speed, and AlloyDB keeps that compatibility.
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
Objectsflowchart TD
Q{"What do you need?"}
Q -->|"PostgreSQL with high performance"| A0["AlloyDB"]
Q -->|"Global strong consistency"| A1["Spanner"]Key point: AlloyDB is PostgreSQL-compatible.
Why the other options are wrong
- B. Bigtable
- Bigtable is not relational.
- C. Pub/Sub
- Pub/Sub carries messages.
- D. Dataflow
- Dataflow processes data.

