Loading content
Databases are structured systems for storing, querying and managing persistent data. They provide models for organizing records, ensure consistency and durability, and enable efficient access patterns across applications. Databases underpin analytics, transactional systems and integration layers in modern software architectures.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A database is a structured system for storing persistent data, making it queryable, and managing it under defined rules. It underpins applications, analytics, and integration whenever data must stay reliable and usable across time and multiple systems.
Databases emerged from the need to do more than collect data: they had to keep it durable, shared, and controlled. Direct-access storage media and DBMSs made it practical to manage larger data sets efficiently. Edgar F. Codd’s 1970 relational model shaped tables, querying, and later SQL as the dominant approach.
Think of a database as a three-layer arrangement. A schema defines what shape the data may take. The DBMS receives requests, checks rules, and coordinates reads, writes, and concurrent access to storage. Transactions, indexes, and recovery mechanisms keep the data useful under load, failure, and parallel use.
It determines how data, relationships, and values are organized logically.
The management software brings storage, queries, permissions, and operations together.
The schema describes the allowed structure and the main rules for the data.
A query language is used to read, filter, change, and aggregate data.
Related changes are grouped so they remain controlled and traceable.
Multiple access paths are coordinated, and failures can be handled through logs and backups.
A database is essential when several applications must use the same data consistently, or when correctness, resilience, and targeted querying matter more than simple storage. The choice of model brings trade-offs: stronger integrity often reduces flexibility, heavy write loads need different optimization than analytical queries, and operations require discipline around backups, indexing, and migrations.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.