EIP key terms

Enterprise architecture is a structured practice that documents how business strategy, processes, applications, data, and technology fit together, guiding coordinated change across an organization.

An integration pattern is a reusable, documented approach for connecting systems, describing how messages or data flow between applications, including routing, transformation, and error handling responsibilities.

A canonical data model is a shared, application-neutral representation of business data used to decouple systems, so each integration maps to one common format rather than to every other system.

An API gateway is an intermediary that receives client requests, enforces authentication and rate limits, routes traffic to backend services, and can transform requests or responses before returning them.

Event-driven architecture is a design style in which systems publish and react to business events asynchronously, allowing loose coupling and near real-time responses without direct request-response dependencies.

A message broker is middleware that receives, stores, and forwards messages between producers and consumers, enabling asynchronous communication, decoupling, and reliable delivery even when systems are temporarily unavailable.

Service-oriented architecture structures software as interoperable services with defined contracts, so capabilities can be reused and combined across applications, often through standardized interfaces and loose coupling.

Data governance is the decision-making framework of roles, policies, and processes that defines who may access, change, and steward data, ensuring quality, privacy, and regulatory compliance.

Master data management is a discipline that creates and maintains trusted, consistent definitions and records for core entities such as customers, products, and suppliers across multiple systems.

Data lineage records the origin, transformations, and movement of data from source to report, helping teams trace errors, assess impact, and demonstrate compliance during audits.

Data quality is the degree to which data is accurate, complete, timely, consistent, and fit for its intended use, typically measured through defined dimensions, rules, and monitoring.

A data warehouse is a centralized, structured repository that consolidates cleaned and modeled data from many sources to support reporting, analysis, and business intelligence.

A data lake is a storage repository that holds large volumes of raw and processed data in native formats until needed, supporting diverse analytics, machine learning, and exploratory use.

Extract, transform, load (ETL) is a data integration process that pulls data from sources, cleans and reshapes it, then writes it into a target repository for analysis.

A data catalog is an organized inventory of data assets with metadata such as owners, definitions, locations, and usage, helping users find and trust suitable datasets.

A dimensional model organizes analytical data into fact tables containing measures and dimension tables containing descriptive attributes, making queries simple and intuitive for business users.

Zero trust is a security model that assumes no implicit trust based on network location, requiring continuous verification of identity, device health, and least-privilege access for every request.

Role-based access control grants permissions based on job roles rather than individual identities, simplifying administration and reducing excessive access when people change positions.

Least privilege is the principle of granting users and systems only the minimum access needed to perform their duties, limiting potential damage from misuse or compromised accounts.

A risk register is a structured log of identified risks, recording likelihood, impact, owner, and mitigation status so that leadership can prioritize and monitor treatment.

Threat modeling is a structured analysis that identifies likely attackers, valuable assets, entry points, and weaknesses early in design, so controls can be chosen before code is written.

Identity federation lets separate organizations trust a shared identity provider, allowing users to authenticate once and access multiple applications without separate credentials.

A business impact analysis identifies critical business functions and estimates the consequences of disruption over time, producing recovery priorities and targets for continuity and disaster planning.

The software development life cycle is the structured sequence of phases from requirements and design through build, test, deployment, and maintenance used to deliver reliable systems.

Requirements traceability is the practice of linking each requirement to its design elements, code, tests, and approvals, making it possible to verify coverage and assess change impact.

A change advisory board is a group that reviews proposed production changes, assesses risk and scheduling, and approves or rejects them to protect service stability.

DevOps is a culture and set of practices that combines development and operations, emphasizing automation, shared ownership, continuous integration, and rapid feedback to deliver software safely.

A RACI matrix assigns each task or decision four roles-responsible, accountable, consulted, and informed-clarifying ownership and communication across project participants.

A stage gate is a governance checkpoint where a project's progress, business case, and risks are reviewed before funding and work continue to the next phase.

A definition of done is a shared checklist of conditions that work must satisfy before it is considered complete, promoting consistent quality and reducing hidden rework.

Infrastructure as code is the practice of defining servers, networks, and cloud resources in version-controlled files so environments can be provisioned repeatably and audited.

Auto-scaling automatically adjusts computing capacity up or down in response to demand signals, maintaining performance during peaks while controlling cost during quiet periods.

Container orchestration automates the deployment, scaling, networking, and recovery of containerized workloads across clusters of hosts, reducing manual effort and improving resilience.

A service level agreement is a contract between a provider and customer that specifies measurable service targets such as availability, response time, and remedies for missed targets.

A recovery time objective is the maximum acceptable duration for restoring a service after disruption, guiding backup design, staffing, and disaster recovery testing priorities.

Observability is the ability to understand a system's internal state from its outputs-logs, metrics, and traces-so teams can detect and diagnose problems quickly.

A virtual private cloud is an isolated network segment within a public cloud where organizations control addressing, subnets, routing, and security boundaries for their resources.