Top 100 Vocabulary for Adults | Database & Platform Professionals
Database and platform vocabulary is the language of preserving trustworthy state while many systems read, write, fail and recover at once. Professionals need to reason about schemas, transactions, performance, replication, access and resilience without confusing faster queries with better data architecture.
This profession-specific flagship belongs to the eduKate Adult Vocabulary for Professionals system. It complements Data & Analytics Professionals, Cloud & DevOps Professionals and Software & Technology Professionals.
The Four Banks
Data Structures & Query: database, table, row, column, schema, relation, primary key, foreign key, index, query, SQL, join, filter, aggregation, view, materialised view, stored procedure, trigger, constraint, normalisation, denormalisation, partition, shard, metadata, catalogue.
Transactions & Consistency: transaction, ACID, atomicity, consistency, isolation, durability, commit, rollback, lock, deadlock, concurrency, serialisation, versioning, snapshot, idempotency, integrity, referential integrity, duplicate, conflict, replication, replica, primary, failover, quorum, consistency model.
Performance & Reliability: latency, throughput, query plan, optimiser, scan, seek, cache, buffer, connection pool, bottleneck, load, capacity, utilisation, slow query, monitoring, metric, log, alert, backup, restore, recovery, point-in-time recovery, redundancy, availability, resilience.
Platform & Governance: platform, service, API, data access, role, permission, least privilege, encryption, secret, audit log, retention, archival, lifecycle, migration, compatibility, dependency, upgrade, patching, maintenance window, service level, ownership, data lineage, governance, compliance, stewardship.
Top 100 Database & Platform Vocabulary: Working Meanings
| # | Word | Professional meaning |
|---|---|---|
| 1 | Database | A system designed to store, organise and retrieve data. |
| 2 | Table | A structured collection of rows and columns. |
| 3 | Row | One record in a relational table. |
| 4 | Column | A defined attribute stored for each row. |
| 5 | Schema | The formal structure defining data objects and relationships. |
| 6 | Relation | A relational data structure representing sets of tuples. |
| 7 | Primary key | A field or set of fields uniquely identifying a row. |
| 8 | Foreign key | A field linking a record to a key in another table. |
| 9 | Index | A data structure accelerating retrieval at storage and maintenance cost. |
| 10 | Query | A request to retrieve or modify data. |
| 11 | SQL | A language commonly used to work with relational databases. |
| 12 | Join | An operation combining related records from multiple tables. |
| 13 | Filter | A condition restricting returned records. |
| 14 | Aggregation | Combining detail into summary values. |
| 15 | View | A stored query presented as a virtual table. |
| 16 | Materialised view | A physically stored result of a query refreshed under defined rules. |
| 17 | Stored procedure | A named database-side program performing defined operations. |
| 18 | Trigger | Logic automatically executed in response to specified database events. |
| 19 | Constraint | A rule enforcing allowed data states. |
| 20 | Normalisation | Structuring relational data to reduce unnecessary redundancy and anomalies. |
| 21 | Denormalisation | Intentional duplication or restructuring to improve access performance. |
| 22 | Partition | A division of a logical table or dataset into manageable pieces. |
| 23 | Shard | A horizontal partition distributed across separate database resources. |
| 24 | Metadata | Information describing database objects and data. |
| 25 | Catalogue | A system record describing database structures and objects. |
| 26 | Transaction | A unit of database work treated as one logical operation. |
| 27 | ACID | Atomicity, consistency, isolation and durability: core transaction properties. |
| 28 | Atomicity | The property that a transaction completes fully or not at all. |
| 29 | Consistency | Preservation of defined data rules before and after transactions. |
| 30 | Isolation | Control of how concurrent transactions affect one another. |
| 31 | Durability | Persistence of committed changes despite failure. |
| 32 | Commit | Making transaction changes permanent. |
| 33 | Rollback | Reversing uncommitted transaction changes. |
| 34 | Lock | A mechanism controlling concurrent access to data. |
| 35 | Deadlock | A condition where transactions wait indefinitely for resources held by each other. |
| 36 | Concurrency | Multiple operations progressing during overlapping time. |
| 37 | Serialisation | Ordering concurrent operations so results match an acceptable serial execution. |
| 38 | Versioning | Maintaining distinct states of data, schema or platform components. |
| 39 | Snapshot | A point-in-time view or copy of data. |
| 40 | Idempotency | The property that repeating an operation produces the same intended end state. |
| 41 | Integrity | Accuracy and internal correctness of stored data. |
| 42 | Referential integrity | Consistency of relationships between referenced records. |
| 43 | Duplicate | An unintended repeated representation of the same entity or event. |
| 44 | Conflict | Competing data changes that cannot be applied together without resolution. |
| 45 | Replication | Copying data between database systems for scale or resilience. |
| 46 | Replica | A copy of database data maintained from another source. |
| 47 | Primary | The authoritative database node accepting specified writes in a replication topology. |
| 48 | Failover | Transfer of service to another database node after failure. |
| 49 | Quorum | A minimum number of participants required to agree on an operation. |
| 50 | Consistency model | The guarantees a distributed data system makes about when updates become visible. |
| 51 | Latency | The delay before a database operation completes. |
| 52 | Throughput | The volume of operations completed over time. |
| 53 | Query plan | The database engine’s chosen sequence for executing a query. |
| 54 | Optimiser | The component selecting an efficient query plan. |
| 55 | Scan | Reading many or all rows to find matching data. |
| 56 | Seek | Using an index to locate matching data directly. |
| 57 | Cache | Fast storage holding frequently accessed data. |
| 58 | Buffer | Memory used temporarily during database input and output. |
| 59 | Connection pool | A managed set of reusable database connections. |
| 60 | Bottleneck | A limiting resource restricting overall database performance. |
| 61 | Load | The amount of work placed on a database system. |
| 62 | Capacity | The amount of workload a system can handle under stated conditions. |
| 63 | Utilisation | The proportion of available resource currently used. |
| 64 | Slow query | A query whose execution time is materially longer than expected or acceptable. |
| 65 | Monitoring | Ongoing observation of database health and performance. |
| 66 | Metric | A quantitative measure of database behaviour. |
| 67 | Log | A recorded sequence of database events or changes. |
| 68 | Alert | A notification indicating a potentially important condition. |
| 69 | Backup | A recoverable copy of data. |
| 70 | Restore | Returning data from a backup into service. |
| 71 | Recovery | Restoration of usable database state after failure. |
| 72 | Point-in-time recovery | Restoring a database to a selected historical point using backups and logs. |
| 73 | Redundancy | Additional copies or components preserving service after failure. |
| 74 | Availability | The proportion of time the database service is usable. |
| 75 | Resilience | The ability to withstand disruption and recover. |
| 76 | Platform | A shared technical foundation supporting applications or teams. |
| 77 | Service | A defined technical capability offered to users or applications. |
| 78 | API | An interface enabling software systems to interact. |
| 79 | Data access | Permission and mechanism for retrieving or modifying data. |
| 80 | Role | A named group of permissions assigned to identities. |
| 81 | Permission | An authorised action on a resource. |
| 82 | Least privilege | Granting only the minimum access required. |
| 83 | Encryption | Transformation of data to protect confidentiality. |
| 84 | Secret | Sensitive authentication or cryptographic material. |
| 85 | Audit log | A traceable record of important access and change events. |
| 86 | Retention | The period for which data is kept. |
| 87 | Archival | Moving infrequently used data into long-term storage. |
| 88 | Lifecycle | The stages through which data or platform components pass over time. |
| 89 | Migration | Moving data or systems from one platform or version to another. |
| 90 | Compatibility | The ability of systems or versions to work together correctly. |
| 91 | Dependency | A system or service on which another component relies. |
| 92 | Upgrade | Moving to a newer version or capability level. |
| 93 | Patching | Applying fixes for defects or vulnerabilities. |
| 94 | Maintenance window | A scheduled period reserved for system maintenance. |
| 95 | Service level | A defined standard for platform availability or performance. |
| 96 | Ownership | Clear responsibility for a dataset, platform or service. |
| 97 | Data lineage | The documented path showing where data originated and how it changed. |
| 98 | Governance | The structure of standards, ownership and accountability. |
| 99 | Compliance | Conformity with applicable data and platform requirements. |
| 100 | Stewardship | Responsible long-term management of shared data and platform resources. |
Fast Queries Can Hide Fragile Architecture
A query may be fast today because the dataset is small, the cache is warm or traffic is low. Platform professionals ask what happens when concurrency rises, data grows, replicas lag or recovery is required.
Scenario: Database Latency Suddenly Rises
Check workload, slow-query patterns, locks, storage, connection saturation, recent schema changes and replica health. Treat latency as a symptom across layers rather than immediately blaming the database engine.
Seven-Day Database & Platform Vocabulary Plan
| Day | Practice |
|---|---|
| 1 | Map schema, keys, indexes and relationships. |
| 2 | Separate transactions, locks and isolation. |
| 3 | Trace a query through plan, index and storage. |
| 4 | Model replication and failover. |
| 5 | Practise backup, restore and recovery language. |
| 6 | Recall 75+ database terms by function. |
| 7 | Write a one-page platform review balancing performance, integrity and resilience. |
Continue the Digital Experience Wing
Conclusion
Database and platform vocabulary helps professionals preserve trustworthy state under load and failure. It connects schema design, transactions, performance, access and recovery into one operational system.