JP
ENWhat's TERIOS?
TERIOS is a next-generation loosely coupled architecture technology independently developed by Lambda LLC.
It describes everything from frontend to backend and operations in a unified DSL, completely absorbing implementation differences.
Loosely Coupled Architecture Comparison
We compared major architecture patterns with TERIOS across 11 dimensions.
| Criteria | TERIOS | Hexagonal/ Clean/Onion |
Microservices/ SOA |
MDD/MDA | Low-Code/ No-Code |
|---|---|---|---|---|---|
| Abstraction Coverage | ◎ | ○ | △ | ○ | △ |
| FE/BE Cross-cutting DSL | ◎ | × | × | △ | △ |
| Implementation Abstraction | ◎ | ○ | △ | ○ | △ |
| Data-Driven Degree | ◎ | △ | △ | ○ | ○ |
| No Post-Generation Edits | ◎ | ○ | ○ | △ | △ |
| Polymorphism Control | ◎ | ○ | △ | △ | × |
| Testability | ◎ | ○ | △ | △ | △ |
| Operations/Deploy Decoupling | ○ | △ | ◎ | △ | △ |
| Extensibility/Rewiring | ◎ | ○ | ○ | △ | △ |
| Black Box Nature | × | × | △ | △ | ◎ |
| Escape Hatch | ◎ | ◎ | ○ | △ | × |
Rating Legend
- ... Exceptionally strong
- ... Sufficiently capable
- ... Partial support or limitations
- ... Mostly unsupported
Evaluation Criteria Details
Abstraction Coverage
How much of the system can be covered by a single abstraction (DSL, etc.)
FE/BE Cross-cutting DSL
Can frontend, backend, and operations be described in the same DSL
Implementation Abstraction
How well can it absorb technical differences in DB/auth/external APIs
Data-Driven Degree
Can rules and mappings be controlled via data (DSL/JSON, etc.)
No Post-Generation Edits
Whether manual edits after code generation are unnecessary
Polymorphism Control
Freedom in polymorphism and advanced extension techniques
Testability
Ease of automated testing and mocking
Operations/Deploy Decoupling
Degree of coupling during operations and deployment
Extensibility/Rewiring
Ease of adding new features or changing configurations
Black Box Nature
Degree to which internal structure is hidden
Escape Hatch
Whether custom implementations outside the framework are possible
Conclusion
In terms of achieving "loose coupling," virtually no general-purpose architecture matches TERIOS in scope—where DSL penetrates frontend/backend and absorbs implementation differences.
While similar philosophies exist, TERIOS excels in the "coverage" of abstraction (end-to-end from FE/BE to operations) and absorption of implementation freedom.
Where TERIOS Excels
Abstraction Coverage
UI event handling (triad), services, validation, DTO conversion, security, and gateway are unified under the same DSL vocabulary.
Implementation Abstraction
Wraps concrete technologies for DB, messaging, Web/API, and authentication in DSL conventions (rule providers, transformers, validators, etc.).
Change Flexibility
Data-driven (JSON/DSL) rewiring of rules and mappings minimizes code modifications.
Consistent Decoupling Granularity
Crosses structural decoupling (layers/boundaries) × implementation decoupling (tech differences) × operational decoupling (deploy paths/gateways) in a single mechanism.
Similar but Different Scope
The following architectures aim for loose coupling but have limited scope.
Hexagonal (Ports & Adapters)
Separates domain from externals (UI/DB/messaging) via ports.
Strong structural decoupling, but unified cross-language/layer DSL is not the goal.
Clean Architecture / Onion
Domain-centric with dependency direction rules.
Easy to swap implementations, but doesn't extend to FE/BE unified abstraction.
Microkernel (Plug-in Architecture)
Loosely couples feature extensions via core + plugins.
High add-in interchangeability, but doesn't unify the description language across the entire app.
SOA / Microservices
Loosely couples services via protocols.
Strong organizational/operational decoupling, but internal implementation/language abstraction is not the goal.
CQRS + Event Sourcing
Reduces coupling via read/write separation and event storage.
Strong temporal decoupling for data changes, but not a cross-layer DSL.
EDA (Event-Driven) / Actor Model
Reduces coupling via asynchronous messaging.
Strong runtime decoupling, but language/framework differences remain at design time.
DI/IoC & Thorough Polymorphism
Delays implementation decisions via injection.
Strengthens local decoupling. System-wide DSL optimization is a separate layer.
Interested in TERIOS?
For detailed explanations or implementation consultations, please feel free to contact us.