DT008
Build thin API wrappers around legacy systems immediately to bring them within the secure, auditable integration architecture required by NIS2 without waiting for full replacement.
CyberTRIZ analysis · Process contradiction DT008 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Greater API-First Architecture Adoption vs. Legacy System Compatibility
Business Context. Adopting an API-first architecture improves flexibility and enables faster integration for future systems, but many legacy systems were never designed to expose the modern APIs this architecture assumes.
Process TRIZ Resolution. Rather than waiting for legacy systems to be replaced before adopting API-first principles, organizations should build a thin API wrapper layer around legacy systems, exposing their functionality through modern interfaces without requiring the legacy system itself to change.
Applicable TRIZ Principles
Principle 24 (Intermediary) builds an API wrapper layer that exposes legacy functionality through modern interfaces.
Principle 28 (Mechanics Substitution) replaces direct legacy integration with a modern API layer where feasible.
Principle 5 (Merging) combines legacy and modern systems under a unified API architecture.
Expected Outcome
Modern API-first architecture
Preserved legacy system functionality
Faster future integration capability
Reduced dependency on full legacy replacement
Decision Indicators
API-first adoption has stalled waiting for legacy system replacement.
Legacy systems remain isolated from the modern integration architecture.
No wrapper layer exists to expose legacy functionality through APIs.
New integrations cannot connect to legacy systems without custom, one-off work.
Architecture strategy assumes legacy replacement that has not materialized.
If several of these indicators are present, the contradiction is likely active and the Process TRIZ resolution above should be evaluated.