Event representing something meaningful within a business domain.

Software layer containing domain-specific rules and concepts.

Data Transfer Object used to carry data between components.

Selecting a method implementation at runtime.

Metadata attached to data or code elements.

Framework connecting data models with interface components.

Class primarily designed to hold data.

Encryption applied to stored or transmitted data.

Defined format for representing serialized data.

Layer hiding database-specific implementation details.

Group of database servers working together.

Reusing database connections to reduce connection overhead.

Mechanism restricting concurrent access to database data.

Maintaining synchronized copies of database data.

Database action automatically executed by a defined event.

Queue storing messages that cannot be processed successfully.

Build containing settings useful for debugging.

Information mapping compiled code to source code.

Describing desired results rather than execution steps.

Pattern dynamically adding responsibilities to objects.

Parameter with a predefined value if no argument is supplied.

Situation where required dependency versions are incompatible.

Process selecting compatible dependency versions.

Framework managing dependency creation and injection.

File describing deployment configuration.

Planned method for releasing software.

Class inheriting from another class.

Environment used for active software development.

Build intended primarily for development and testing.

Stages involved in developing and maintaining software.

Filesystem structure containing files or other directories.

Navigating filesystem directories, potentially including parent paths.

Processes for restoring systems after major failures.

Computing performed across multiple networked machines.

Lock mechanism coordinated across multiple machines.

Transaction spanning multiple services or databases.

Service containing domain logic not naturally belonging to an entity.