Cross-Module

Definitions

1. Describing behavior, concerns, or dependencies that span more than one module rather than staying isolated inside a single unit. Cross-module issues often need careful coordination because they affect ownership boundaries, interfaces, and change risk.

   In plain English: Involving multiple modules instead of just one.

   Example: "Tracing support became a cross-module concern once request IDs had to pass through transport, business logic, and persistence layers consistently."

Related Terms

• Package
• Platform
• Plugin
• Circular Dependency
• Code Dependency
• Code Load
• Code Module
• Core Module
• Import Hell