A large enterprise is building an OutSystems solution with 15 development teams working on different business domains (HR, Finance, Procurement, Sales). What architectural approach best prevents cross-team coupling while enabling shared data access?
- AOne large monolithic application with all teams working in the same module
- BDomain-driven decomposition: each domain owns its entities and exposes Service Actions fo…
- CEach team builds a separate OutSystems environment
- DUse a shared database schema with stored procedures for all cross-domain data access