Integrations Inventory and Attributes - Classification attributes for the Integrations Inventory

Integrations Inventory and Attributes

Chapter 10. Classification attributes for the Integrations Inventory

Classification attributes position each Integration within the enterprise integration taxonomy — the type of mechanism it uses and the behavioral pattern it implements.

Attribute Name	Maturity	Description and Notes
Integration Type	Crawl	Description — The broad category of integration mechanism — what kind of integration this is at the architectural level. Benefit(s) — Enables portfolio-level analysis of integration patterns. Identifying all SFTP file transfers reveals manual, batch-oriented coupling that is typically a modernization target. Identifying all point-to-point API integrations reveals direct dependencies that bypass integration governance. Source — Manual. Examples — SFTP (Secure File Transfer), ETL (Extract-Transform-Load), ELT (Extract-Load-Transform), AFT (Automated File Transfer), API (Application Programming Interface), Event/Message, Database-to-Database, Webhook, RPA (Robotic Process Automation), EDI (Electronic Data Interchange) Notes — Valid values are enterprise-defined. The examples above are a suggested baseline. Extend to match your organization’s integration taxonomy.
Integration Pattern	Walk	Description — The behavioral or architectural pattern governing how data moves between source and target. Distinct from Integration Type — an API integration can be Request-Response, Publish-Subscribe, or Fire-and-Forget. Benefit(s) — Reveals coupling characteristics and failure mode risk. Synchronous Request-Response integrations create tight coupling and cascading failure risk. Asynchronous Publish-Subscribe integrations decouple systems but require queue governance. Source — Manual. Examples — Request-Response (Synchronous), Publish-Subscribe, Fire-and-Forget, Polling, Streaming, Batch Notes — Integration Type describes the mechanism. Integration Pattern describes the behavioral contract between sender and receiver.

Attribute Name

Maturity

Description and Notes

Integration Type

Crawl

Description — The broad category of integration mechanism — what kind of integration this is at the architectural level.

Benefit(s) — Enables portfolio-level analysis of integration patterns. Identifying all SFTP file transfers reveals manual, batch-oriented coupling that is typically a modernization target. Identifying all point-to-point API integrations reveals direct dependencies that bypass integration governance.

Source — Manual.

Examples — SFTP (Secure File Transfer), ETL (Extract-Transform-Load), ELT (Extract-Load-Transform), AFT (Automated File Transfer), API (Application Programming Interface), Event/Message, Database-to-Database, Webhook, RPA (Robotic Process Automation), EDI (Electronic Data Interchange)

Notes — Valid values are enterprise-defined. The examples above are a suggested baseline. Extend to match your organization’s integration taxonomy.

Integration Pattern

Walk

Description — The behavioral or architectural pattern governing how data moves between source and target. Distinct from Integration Type — an API integration can be Request-Response, Publish-Subscribe, or Fire-and-Forget.

Benefit(s) — Reveals coupling characteristics and failure mode risk. Synchronous Request-Response integrations create tight coupling and cascading failure risk. Asynchronous Publish-Subscribe integrations decouple systems but require queue governance.

Source — Manual.

Examples — Request-Response (Synchronous), Publish-Subscribe, Fire-and-Forget, Polling, Streaming, Batch

Notes — Integration Type describes the mechanism. Integration Pattern describes the behavioral contract between sender and receiver.

Legal Disclaimers