data-review

To review your DynamoDB data model for hot partitions and idempotency, validate your schema design and access patterns against your specific query plans. This prevents performance regressions by ensuring idempotent operations and proper key distribution.

Choosing between DynamoDB and RDS Aurora requires evaluating your access patterns to justify the database selection. Reviewing data persistence ensures clear rationale for either schema based on how your application reads and writes data.

To optimize SQL queries and avoid N+1 behavior and full table scans in RDS, review your query plans and index strategy. Validating relational indexes against your access patterns ensures optimized query performance and correctness.

Your database design needs RDS Proxy configuration for Lambda integration to manage connection pooling and prevent connection exhaustion. Reviewing this runtime integration guidance ensures operational readiness for serverless compute environments.

You need to validate backup, PITR, and KMS encryption requirements for your data persistence layer during operational readiness checks. Reviewing these configurations ensures production reliability and security compliance for your database.