Microsoft Azure Data FundamentalsDescribe how to work with relational data on AzureMedium
A financial company uses Azure Database for PostgreSQL to store customer transaction data. Due to increasing read workloads from reporting and analytics applications, the primary database is experiencing performance bottlenecks. The company needs to offload these read-heavy queries to maintain optimal performance for write operations on the primary database. Which Azure Database for PostgreSQL feature should they implement?
- AHigh Availability
- BPoint-in-time restore
- CConnection Pooling
- DRead Replicas
Show answer & explanationAnswer & explanation
Correct answer: D. Read Replicas
Read Replicas in Azure Database for PostgreSQL are specifically designed to offload read-intensive workloads from the primary database. They provide asynchronously replicated copies of the primary, allowing reporting and analytics queries to run without impacting the primary's performance.
Why the other options are wrong
- A. High Availability ensures continuous operation in case of failures but does not inherently scale out read operations to multiple servers for performance improvement.
- B. Point-in-time restore is a disaster recovery feature used to restore a database to a previous state, not for offloading read workloads.
- C. Connection Pooling manages and reuses database connections to reduce overhead, but it does not offload read queries to a separate server.
Azure DB for PostgreSQL Read Replicas
Asynchronously replicated copies of an Azure Database for PostgreSQL primary server, used to scale out read-heavy workloads and improve performance for reporting and analytics.
- Offloads read traffic from the primary server.
- Data is asynchronously replicated.
- Improves performance for read-intensive applications.
- Can be promoted to primary in a disaster recovery scenario.
Memory trick: Read Replicas replicate to relieve read pressure.