query
A request to a database for data, written in SQL, that returns a set of rows as its answer.
In more detail
Most queries are SELECT statements that name the columns, the tables and the conditions for the rows you want. Because SQL describes the result rather than the steps, the database's query planner chooses how to fetch it.
Example
In AWS: A request that asks a database for the data matching some conditions.Related terms
- partition key — The DynamoDB attribute whose value decides which storage partition an item lives in, and which every query must name.
- SQL — The standard language for defining, querying and changing data in a relational database.
- secondary index — An extra copy of a DynamoDB table’s data organised by different keys, giving the application another way to query it.
- SELECT — The SQL statement that reads data: it names the columns you want in the answer and, with FROM, the tables they come from.
- query planner — The part of the database that turns a SQL query into a plan, choosing among indexes, scans and join orders.
- index — A separate, sorted structure a database keeps alongside a table so it can find matching rows without reading them all.
- access pattern — How an application actually reads and writes its data: how often, how much, by which key and how quickly it needs answers.
- fan-out — Sending one request or message on to many recipients or services at once.
Taught in
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- Managed Relational Databases (RDS) — Cloud Infrastructure & Hyperscaler Architecture
- NoSQL and DynamoDB — Cloud Infrastructure & Hyperscaler Architecture
- When to Pick Which Database — Cloud Infrastructure & Hyperscaler Architecture
- Why Tables And Relations Beat Files — PostgreSQL, Indexing & Relational Data Modeling
- The SELECT Statement And Projection — PostgreSQL, Indexing & Relational Data Modeling
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- The Storage Decision: Relational Versus Document — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Partitioning, Sharding And Hot Keys — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Capacity Planning As A Design Input — Scalable System Design & Distributed Architecture
- Worked Design Two: A Global Chat System — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture