Search the practice set

126 questions, 454 terms and 400 topics in 20 areas.

19 results for “Vector Databases”

Terminology · 14
term

Vector Database

A store optimised for approximate nearest-neighbour search over high-dimensional embeddings.

AI-Era Architecture
term

Version Vector

A per-replica counter set that lets a system tell whether one version causally descends from another or whether the two are genuinely concurrent.

Clocks & Ordering
term

Block Storage

A virtual disk attached to one instance at a time, presented as raw blocks and formatted with a filesystem — the storage databases and stateful workloads run on.

Cloud Storage
term

Connection Pool

A fixed set of reusable database connections shared by an application's requests, and one of the most common hidden capacity ceilings.

Performance & Capacity
term

Connection Proxy

A pooling layer between applications and a managed database that multiplexes many client connections onto a small number of database connections.

Cloud Databases
term

Database Index

A secondary structure that lets the engine find rows without scanning, trading write cost and storage for read speed.

Data Architecture
term

Embedding

A dense numeric vector representing a piece of content, positioned so that semantically similar content sits nearby.

AI-Era Architecture
term

Indexing Strategy

Choosing the set of indexes a table carries by working backwards from its actual queries, and accepting the write cost that each one adds.

Data Architecture
term

Provisioned vs Serverless Capacity

Paying for a fixed database size continuously, versus paying for capacity consumed with automatic scaling — a crossover decision driven by duty cycle.

Cloud Databases
term

Query Plan

The database's chosen strategy for executing a query, and the first thing to look at when one is slow.

Data Architecture
term

Read Replica

A copy of a database that receives changes from the primary and serves read-only queries, spreading read load.

Data Architecture
term

SQL vs NoSQL

A choice driven by access patterns, consistency requirements and query flexibility — not by data volume, which is the reason usually given.

Architecture Decision-Making
term

Sharding

Splitting one dataset across multiple independent databases by a partition key, so that each holds a disjoint subset.

Data Architecture
term

Write-Ahead Log

Recording every change to a durable sequential log before applying it, so that a crash can be recovered by replaying the log.

Data Architecture