Onion Architecture
E679172
Onion Architecture is a software architectural pattern that emphasizes a domain-centric design with concentric layers that enforce dependency inversion and separation of concerns.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Onion Architecture canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7666613 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Onion Architecture Context triple: [Clean Architecture, influencedBy, Onion Architecture]
-
A.
Clean Architecture
Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
-
B.
Flux architecture
Flux architecture is a unidirectional data flow pattern for building client-side web applications, originally introduced by Facebook as an alternative to traditional MVC.
-
C.
Portland Pattern Repository
Portland Pattern Repository is an early and influential online collection of software design patterns and related discussions, created by Ward Cunningham as part of the first wiki.
-
D.
Domain-Driven Design: Tackling Complexity in the Heart of Software
"Domain-Driven Design: Tackling Complexity in the Heart of Software" is a seminal software engineering book by Eric Evans that introduces the domain-driven design approach for managing complexity in large, business-focused software systems.
-
E.
Dependency Inversion Principle
The Dependency Inversion Principle is an object-oriented design guideline that promotes decoupling by having high-level and low-level modules depend on shared abstractions rather than concrete implementations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Onion Architecture Target entity description: Onion Architecture is a software architectural pattern that emphasizes a domain-centric design with concentric layers that enforce dependency inversion and separation of concerns.
-
A.
Clean Architecture
Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
-
B.
Flux architecture
Flux architecture is a unidirectional data flow pattern for building client-side web applications, originally introduced by Facebook as an alternative to traditional MVC.
-
C.
Portland Pattern Repository
Portland Pattern Repository is an early and influential online collection of software design patterns and related discussions, created by Ward Cunningham as part of the first wiki.
-
D.
Domain-Driven Design: Tackling Complexity in the Heart of Software
"Domain-Driven Design: Tackling Complexity in the Heart of Software" is a seminal software engineering book by Eric Evans that introduces the domain-driven design approach for managing complexity in large, business-focused software systems.
-
E.
Dependency Inversion Principle
The Dependency Inversion Principle is an object-oriented design guideline that promotes decoupling by having high-level and low-level modules depend on shared abstractions rather than concrete implementations.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
architectural style
ⓘ
software architectural pattern ⓘ |
| contrastsWith | layered architecture with outward dependencies ⓘ |
| definesRule |
UI depends on application and domain layers
ⓘ
data access is implemented in outer layers ⓘ dependencies point inwards toward the domain ⓘ infrastructure depends on domain, not vice versa ⓘ inner layers must not depend on outer layers ⓘ |
| emphasizes |
business logic
ⓘ
domain model ⓘ independence from databases ⓘ independence from frameworks ⓘ independence from infrastructure ⓘ independence from user interface ⓘ |
| encourages |
use of dependency injection containers
ⓘ
use of repositories for persistence abstraction ⓘ writing unit tests against domain interfaces ⓘ |
| focusesOn | core domain as the center of the system ⓘ |
| goal |
enable easier replacement of infrastructure
ⓘ
improve testability of domain logic ⓘ isolate business logic from technical concerns ⓘ reduce coupling to frameworks ⓘ support long-term maintainability ⓘ |
| hasDesignPrinciple |
dependency inversion
ⓘ
domain-centric design ⓘ encapsulation of business rules ⓘ loose coupling ⓘ maintainability ⓘ separation of concerns ⓘ testability ⓘ |
| hasLayer |
application layer
ⓘ
core layer ⓘ domain layer ⓘ infrastructure layer ⓘ outer layers ⓘ presentation layer ⓘ |
| organizesCodeAs | concentric layers ⓘ |
| relatedTo |
Clean Architecture
ⓘ
Hexagonal Architecture ⓘ |
| separates |
application services from user interface
ⓘ
business rules from persistence concerns ⓘ domain logic from infrastructure code ⓘ |
| similarConcept | ports and adapters architecture ⓘ |
| supports | domain-driven design ⓘ |
| typicalUseCase |
complex business systems
ⓘ
domain-driven design projects ⓘ enterprise applications ⓘ |
| usesPattern |
dependency inversion principle
ⓘ
interfaces for abstractions ⓘ inversion of control ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Onion Architecture Description of subject: Onion Architecture is a software architectural pattern that emphasizes a domain-centric design with concentric layers that enforce dependency inversion and separation of concerns.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.