Cloud Database Selection Guide

Help me select the right cloud database services for my workloads:

Cloud Provider: [AWS/GCP/AZURE/MULTI-CLOUD]
Workload Descriptions: [DESCRIBE EACH WORKLOAD]
Data Volume: [CURRENT AND PROJECTED DATA SIZE]
Read/Write Patterns: [READ-HEAVY/WRITE-HEAVY/BALANCED]
Consistency Requirements: [STRONG/EVENTUAL/MIXED]
Latency Requirements: [REAL-TIME/NEAR-REAL-TIME/BATCH]

Provide guidance across these six areas:

1. Relational Database Evaluation
- Compare managed relational options such as RDS, Cloud SQL, and Azure SQL Database across supported engines including PostgreSQL, MySQL, and SQL Server. Evaluate Aurora, Cloud Spanner, and Hyperscale for high-throughput and globally distributed relational needs. Assess provisioned versus serverless modes based on traffic patterns and cost profiles. Analyze read replica strategies for read scaling and geographic distribution. Review connection pooling approaches using RDS Proxy, PgBouncer, or built-in pooling. Evaluate migration paths from self-managed databases to managed services. Provide sizing recommendations for CPU, memory, storage IOPS, and connection limits.

2. NoSQL and Document Database Options
- Compare DynamoDB, Firestore, Cosmos DB, and MongoDB Atlas for document and key-value workloads. Evaluate partition key design strategies and access pattern optimization for DynamoDB. Assess Cosmos DB consistency models from strong to eventual and their performance implications. Analyze pricing models including provisioned capacity, on-demand, and reserved capacity. Review secondary index strategies and query flexibility tradeoffs. Evaluate change data capture and streaming capabilities for event-driven architectures. Compare operational overhead across fully managed versus self-managed options.

3. In-Memory and Caching Databases
- Evaluate ElastiCache for Redis, Memorystore, and Azure Cache for Redis for caching and session management. Assess cluster mode versus non-cluster mode configurations. Design cache invalidation strategies including TTL-based, event-driven, and write-through patterns. Evaluate caching layers at application, database, and CDN levels. Compare Memcached versus Redis for specific use cases. Plan for cache warming, failover, and data persistence requirements. Analyze cost versus performance benefits of different instance sizes.

4. Analytics and Data Warehouse
- Compare Redshift, BigQuery, and Synapse Analytics for analytical workloads. Evaluate serverless versus provisioned warehouse models and their cost implications. Assess data lake integration using Redshift Spectrum, BigQuery external tables, or Synapse Serverless SQL. Review columnar storage optimization and partitioning strategies. Evaluate query performance tuning options including sort keys, distribution keys, and materialized views. Compare pricing models based on storage, compute, and query volume. Plan for data ingestion pipelines from operational databases.

5. Specialized Database Services
- Evaluate time-series databases such as Timestream, InfluxDB, or Azure Data Explorer for IoT and metrics. Assess graph databases including Neptune, Neo4j, and Cosmos DB Gremlin API for relationship-heavy data. Review search engines such as OpenSearch, Elasticsearch, and Azure Cognitive Search for full-text search. Evaluate ledger databases like QLDB for immutable audit trails. Assess wide-column stores like Keyspaces and Bigtable for time-stamped analytical data. Match specialized database capabilities to specific workload requirements.

6. Operational Considerations
- Design backup and point-in-time recovery strategies for each database. Plan for cross-region replication and disaster recovery procedures. Evaluate monitoring and performance tuning tools for each engine. Assess encryption at rest and in transit configurations. Plan database version upgrade strategies with minimal downtime. Design connection management and credential rotation procedures. Create a decision matrix template for future database selection decisions.

For each workload provide a primary recommendation and alternative, sizing guidance, estimated monthly cost, migration complexity assessment, and operational burden comparison.