DesignDecisionArchitecture
Dual database architecture
Attributes
| labels | Entity,DesignDecision |
| rationale | Switching to a dual database architecture allows for concurrent read and write operations, eliminating the write lock issue inherent in using a single embedded database like DuckDB. This approach ensures that extraction and querying can happen simultaneously without blocking, thereby improving platform scalability, maintaining data integrity, and enabling real-time analytics during data ingestion. |
| alternatives considered | Using only DuckDB would cause query blocking during data extraction due to its single-writer limitation. Alternatively, implementing snapshots or query queues could temporarily mitigate locking but would not fully solve concurrent access issues at scale. |
| decided by | System architect and development team |
| decision date | 2026-02-28 |
| tier | 2 |
Relationships0 connections
Loading graph...
Related Entities