Dual Database Architecture: Triple Store and Relational Database

The architecture includes both a Triple Store and a Relational Database as complementary technology components under the Data Base grouping. This design enables the system to leverage the distinct strengths of both storage paradigms.

Triple Store

The Triple Store serves as specialized storage for RDF data and semantic knowledge graphs. It is designed to handle graph-based semantic data using the RDF (Resource Description Framework) triple model, which represents information as subject-predicate-object relationships. This makes it ideal for:

• Semantic knowledge representation
• Linked data and ontology management
• Complex relationship queries across interconnected data
• Flexible schema-less data modeling

Relational Database

The Relational Database provides traditional structured data storage using SQL. The implementation uses RDB gen 4 with Postgres v 2.4.5. This component handles:

• Transactional data with ACID compliance
• Structured tabular data with defined schemas
• High-volume operational data
• Complex queries with joins and aggregations

Architectural Rationale

The dual-database architecture is justified by several key factors:

1. Different Data Models: The Triple Store handles graph-based semantic data (RDF triples), while the Relational Database manages structured tabular data. Each technology excels in its respective domain.

2. Dependency Relationship: The Triple Store depends on the Relational Database (relation: "hängt ab von"), indicating that the semantic layer builds upon the foundational structured data layer.

3. Unified Grouping: Both technologies are organized under a common "Data Base" container for architectural clarity, showing they serve complementary purposes within the same architectural domain.

4. Application Persistence: A Database component ("Application-related Persistance_KDD") with stereotype Database represents the application-level persistence layer, ensuring proper data management across both storage systems.

Benefits of the Dual Approach

This architecture enables the system to leverage:
- Semantic flexibility from the Triple Store for knowledge representation and complex relationship queries
- Transactional reliability from the Relational Database for operational data integrity and performance

The combination allows the system to handle both structured operational data and unstructured semantic knowledge without compromising on either dimension.