Differences

This shows you the differences between two versions of the page.

--- reference:system-architecture:infrastructure [2025/08/26 22:08] – [Data governance and security measures] runarbe
+++ reference:system-architecture:infrastructure [2025/08/26 22:10] (current) – runarbe
@@ Line 6: / Line 6: @@
 On top of that, there may be 1000s of users accessing the data retrieval and query interfaces in the API. The following hardware and networking infrastructure requirements are based on the above assumptions.
 ===== 1. Technical requirements specification for database server =====
@@ Line 77: / Line 76: @@
 These configurations are recommended to ensure that the system is scalable, responsive, and reliable for both web and desktop GIS applications.
 ===== 3. Network infrastructure =====
@@ Line 101: / Line 99: @@
 Always consider potential future growth and adjust server capacities as necessary to maintain system performance.
 ===== 4. Client requirements =====
@@ Line 170: / Line 167: @@
 ^ \\ Network Bandwidth| \\ ≥5 Mbps download, <100 ms latency| \\ ≥10 Mbps download, <50 ms latency|
+===== 5. Data governance and security measures =====
-===== 4. Data governance and security measures =====
 In developing the National Addressing System in Oman, maintaining data governance and implementing robust security measures are critical considerations. While it is important not to restrict access to addressing data, prioritising data integrity remains essential. Ensuring that data is accurate, reliable, and trustworthy requires specific strategies.
@@ Line 181: / Line 177: @@
 To maintain the integrity of addressing data, especially in distributed systems, ensuring data concurrency across any distributed copies or caches is crucial. Data concurrency will ensure that different versions of the data remain consistent with each other, preventing discrepancies and potential data conflicts.
+===== 6. Service Level Requirements for Infrastructure =====
-===== Service Level Requirements for Infrastructure =====
 To ensure continuous availability, data integrity, and resilience of the National Addressing System (NAS), the underlying infrastructure must meet clearly defined service level requirements. These requirements are particularly critical given the national importance of address data and the need to support both operational continuity and rapid recovery in the event of an incident.
-==== Disaster Recovery ====
+=== Disaster Recovery ===
 A comprehensive disaster recovery plan will be established to protect the NAS against events such as hardware failures, data corruption, natural disasters, and cyber incidents. The plan will include regular, automated backups of all critical data and system configurations, secure offsite storage, and well-documented procedures for restoring service.
-==== Recovery Time Objective (RTO) ====
+=== Recovery Time Objective (RTO) ===
 The Recovery Time Objective defines the maximum acceptable duration for restoring full service following a disruption. For the NAS, the RTO shall not exceed 4 hours for core database and API services, ensuring that essential address data and integrations remain available to users and stakeholders with minimal downtime. Routine tests of recovery procedures will be conducted to validate adherence to the RTO.
-==== Recovery Point Objective (RPO) ====
+=== Recovery Point Objective (RPO) ===
 The Recovery Point Objective specifies the maximum age of data that may be lost in the event of a failure. For the NAS, the RPO is set at 15 minutes, meaning that backup and replication strategies must ensure that, at most, only the last 15 minutes of transactions could be lost under worst-case scenarios. Incremental backups and near-real-time data replication will be employed to achieve this goal.
-==== Optional Multi-Region Deployment (Middle East/Europe) ====
+=== Optional Multi-Region Deployment (Middle East/Europe) ===
 For public facing applications that might be used by global audiences, it may be possible to further strengthen resilience by supporting geographic redundancy, such parts of the NAS infrastructure as is relevant may optionally be deployed in a multi-region configuration spanning the Middle East and Europe.