Processing analytical requests

🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions.

Platform architecture provides a separate analytical DBMS instance for processing analytical requests to the registry database.

Data is transferred from the registry operational database to the analytical database using PostgreSQL logical replication. It supports real-time data synchronization with minimal latency, selective replication, and flexibility of the analytical database schema and has minimal impact on the performance of the operational database.

Using a separate database for analytical workloads provides the following capabilities and benefits:

  • Query speed: Analytical workloads typically involve complex queries and processing of large data sets. With a separate database optimized for analytics, data can be structured and indexed in ways that increase query performance.

  • Enhanced scalability: Separating the analytical and operational workloads improves scalability. Because analytical queries are typically resource-intensive, they can slow down other processes that depend on the same database. By decoupling the analytical workload, it is possible to scale each workload independently to meet changing demands.

  • Reduced risk: Separating the analytical and operational workloads minimizes the risk of failure of an operational database instance due to errors or performance issues related to analytical queries.

  • Better data management: A separate analytical database ensures a clear separation between operational and analytical data. This makes it easier to enforce policies related to data access, security, and compliance.