Question 220
The service owner asks how to avoid a repeat of: A company wants managed PostgreSQL with minimal schema changes for a moderate single-region transactional service. Which operational check is the best match?
Explanation
Correct Answer
Match database service selection to query and transaction requirements before migration. This is preventive rather than a one-time repair; it addresses the underlying failure: The workload uses ordinary PostgreSQL semantics and does not require globally distributed SQL writes.
Incorrect Answers
This would test row-key prefix entropy with expected ingestion distribution. It is useful when a TimeSeries Bigtable workload uses only a leading timestamp in its row key and struggles at high ingestion rates, but it does not prevent the issue here: the workload uses ordinary PostgreSQL semantics and does not require globally distributed SQL writes.
This safeguard helps protect cases where a company needs short-lived database login credentials but continues distributing shared static SQL users to every microservice. It leaves the main recurring failure untouched: the workload uses ordinary PostgreSQL semantics and does not require globally distributed SQL writes.
The proposed check would include proprietary SQL features and licensing in database-service comparisons, helping with cases where a legacy.NET application uses SQL Server-specific stored procedures and the team plans a zero-change move to PostgreSQL. The recurring exposure described here is that the workload uses ordinary PostgreSQL semantics and does not require globally distributed SQL writes.