Text file defining how to build a container image.

Representation of concepts and relationships in a problem domain.

Software allowing an operating system to control hardware.

Linking libraries during program loading or execution.

Type checking performed largely during program execution.

Graph showing relationships among software dependencies.

File recording exact dependency versions.

Infrastructure where software is deployed and executed.

File describing deployment resources and configuration.

Cache shared across multiple application instances.

Database whose data is distributed across multiple systems.

Lock coordinating access across distributed processes.

Transaction spanning multiple services or databases.

Software design approach centered on business-domain concepts.

Software layer handling data-storage operations.

Metadata attached to data for interpretation or processing.

Expression connecting interface properties to data.

Formal definition of exchanged data structures.

Representing information using a defined encoding scheme.

Component translating between data representations.

Organizing data to reduce redundancy and inconsistency.

Dividing data into manageable subsets.

Maintaining copies of data across systems.

Splitting data across multiple storage nodes.

Checking data against correctness rules.

Reusable pool of database connections.

Software allowing applications to communicate with databases.

Group of database operations treated as a unit.

Queue storing messages that cannot be processed.

Software build containing debugging information or settings.

Process determining and retrieving required dependencies.

Reverting a deployment to an earlier version.

Planned method for releasing software.

Environment used for active software development.

Build intended primarily for development and testing.

Dependency needed for development but not normal runtime.

Stages involved in creating and maintaining software.