Thursday, February 26, 2026
๐Ÿ›ก๏ธ
Adaptive Perspectives, 7-day Insights
Technology

The Cloud Database Landscape in 2026

A conversation about our cloud data strategy sent me down a rabbit hole. I asked Claude to help me map every database option across AWS, Azure, Google Cloud, and beyond.

The Cloud Database Landscape in 2026
Image generated by ChatGPT

We had a meeting at the office today that touched on our cloud data strategy. Much of our data currently lives in on-premises instances of Microsoft SQL Server. The conversation surfaced a question that needed answering before we can plan anything: what are our options?

After the meeting I asked Claude to help me map the full landscape. What started as a quick reference turned into a comprehensive catalog of every cloud database service I could find across the major providers โ€” and a few independent platforms for good measure.

This post is the result. It’s long. It’s meant to be a reference, not a narrative. Bookmark it.

Amazon Web Services

AWS has the broadest database portfolio of the major cloud providers. The full lineup spans relational, NoSQL, document, graph, time-series, in-memory, and analytics services.

ServiceManagementLicensingMigration EffortRelative CostServerless
SQL Server on EC2Self-managedBYOL or includedLowHigherNo
RDS for SQL ServerFully managedLicense includedLowMediumNo
RDS Custom for SQL ServerSemi-managedBYOL or includedLowMediumNo
Aurora PostgreSQLFully managedNo license feeMedium (with Babelfish)MediumYes (v2)
Aurora MySQLFully managedNo license feeHighMediumYes (v2)
Aurora DSQLServerless, distributedNo license feeHighVariesYes
RDS for PostgreSQLFully managedOpen sourceHighLowerNo
RDS for MySQLFully managedOpen sourceHighLowerNo
RDS for MariaDBFully managedOpen sourceHighLowerNo
RDS for OracleFully managedBYOL or includedHighHigherNo
RDS for Db2Fully managedBYOL or marketplaceHighHigherNo
RedshiftFully managed warehouseNo license feeHigh (analytics)Medium-HigherYes
DynamoDBServerless NoSQLNo license feeHigh (re-architecture)LowerYes
NeptuneFully managed graphNo license feeHighMedium-HigherYes
DocumentDBFully managed documentNo license feeHighMediumYes
KeyspacesServerless wide-columnNo license feeHighLowerYes
TimestreamFully managed time-seriesOpen source (InfluxDB)HighMediumNo
ElastiCacheFully managed cacheOpen sourceN/ALowerYes
MemoryDBFully managed in-memoryOpen sourceN/AMedium-HigherNo
OpenSearch ServiceFully managed searchOpen sourceN/AMedium-HigherYes

ElastiCache, MemoryDB, and OpenSearch are complementary services โ€” they’re not SQL Server replacements but are commonly deployed alongside a primary database for caching, durable in-memory workloads, and search, respectively. Aurora PostgreSQL with Babelfish deserves special mention: it accepts T-SQL and the TDS wire protocol, which can significantly reduce migration effort for SQL Server applications. Aurora DSQL is the newest entrant, a fully serverless distributed SQL database with active-active multi-region support that went GA in May 2025.

A word on DynamoDB. The table above marks it as “High” migration effort from SQL Server, and that’s accurate โ€” you can’t take a relational schema and drop it into a NoSQL key-value store. But DynamoDB isn’t trying to replace SQL Server. It shines in a completely different set of use cases: web and mobile backends with predictable access patterns, session management, user profiles, real-time leaderboards, IoT telemetry, and any workload where you need single-digit-millisecond reads at virtually any scale. I use DynamoDB for all of my personal web projects. It’s serverless, scales to zero cost when idle, handles traffic spikes without provisioning, and pairs naturally with Lambda and API Gateway. If you’re building something new on AWS rather than migrating something old, it’s worth serious consideration โ€” just don’t try to force a relational workload into it.

Microsoft Azure

For SQL Server shops, Azure is the most natural starting point โ€” same vendor, same engine. Azure offers the broadest set of SQL Server-compatible managed services, including Azure SQL Managed Instance, which provides roughly 95% compatibility with on-premises SQL Server โ€” including SQL Agent, CLR, cross-database queries, and linked servers.

ServiceManagementLicensingMigration EffortRelative CostServerless
SQL Server on Azure VMSelf-managedBYOL or includedLowVariesNo
Azure SQL DatabaseFully managedBYOL (AHB) or includedMediumMediumYes
Azure SQL Elastic PoolFully managedBYOL (AHB) or includedMediumLower-MediumNo
Azure SQL Managed InstanceFully managedBYOL (AHB) or includedLowMedium-HigherNo
Azure DB for MySQLFully managedOpen sourceHighLowerNo
Azure DB for PostgreSQLFully managedOpen sourceHighLowerNo
Cosmos DB for NoSQLFully managed documentNo license feeHighVariesYes
Cosmos DB for MongoDBFully managed documentNo license feeHighVariesYes
Cosmos DB for CassandraFully managed wide-columnNo license feeHighVariesYes
Cosmos DB for GremlinFully managed graphNo license feeHighVariesYes
Cosmos DB for TableFully managed key-valueNo license feeHighMediumYes
Cosmos DB for PostgreSQLDistributed relationalOpen source (Citus)HighMediumNo
Azure Synapse AnalyticsFully managed warehouseNo license feeMedium-High (analytics)VariesYes (serverless pools)
Azure Data ExplorerFully managed analyticsNo license feeHighMedium-HigherNo
Azure Managed RedisFully managed cacheNo license feeN/AMediumNo
Azure Table StorageFully managed key-valueNo license feeHighLowerYes
Azure Confidential LedgerFully managed ledgerNo license feeHighLowerYes
Managed Instance for CassandraManaged instanceOpen sourceHighMediumNo

Azure Hybrid Benefit (AHB) lets you apply existing SQL Server licenses with Software Assurance to Azure SQL services, saving up to 55%. Combined with reserved capacity, savings can reach 80%. Azure SQL Database offers a serverless compute tier that auto-pauses when idle โ€” you pay nothing for compute during idle periods. Azure Database for MariaDB was retired in September 2025. Azure Cache for Redis is being retired in favor of Azure Managed Redis. On the horizon: Azure HorizonDB, a PostgreSQL-compatible cloud-native database in private preview, and Microsoft Fabric Databases, a unified SaaS data platform that went GA in November 2025.

Google Cloud Platform

Google Cloud has a smaller database portfolio than AWS or Azure, but it includes some notably differentiated cloud-native options โ€” particularly Cloud Spanner and AlloyDB.

ServiceManagementLicensingMigration EffortRelative CostServerless
SQL Server on Compute EngineSelf-managedBYOL or includedLowVariesNo
Cloud SQL for SQL ServerFully managedLicense includedLowMediumNo
Cloud SQL for MySQLFully managedOpen sourceHighLowerNo
Cloud SQL for PostgreSQLFully managedOpen sourceHighLowerNo
AlloyDB for PostgreSQLFully managed, cloud-nativeProprietary (PG-compatible)HighMedium-HigherNo
Cloud SpannerFully managed, globalProprietaryHighHigherYes (autoscaler)
BigQueryServerless warehouseProprietaryHigh (analytics)Lower-VariesYes
Cloud BigtableFully managed wide-columnProprietaryHighHigher (small scale)Autoscaling
FirestoreServerless documentProprietaryHighLowerYes
Firebase Realtime DatabaseServerless JSONProprietaryHighLowerYes
Memorystore for RedisFully managed cacheOpen sourceN/AMediumNo
Memorystore for ValkeyFully managed cacheOpen source (BSD)N/AMediumNo

AlloyDB is Google’s cloud-native PostgreSQL-compatible engine, claiming 4x faster transactions and up to 100x faster analytics than standard PostgreSQL. It also offers AlloyDB Omni, a downloadable version that runs on-premises, in containers, or on other clouds. Cloud Spanner is Google’s globally distributed, strongly consistent relational database supporting both GoogleSQL and PostgreSQL dialects, with recently added graph, full-text search, and vector search capabilities. It offers a managed autoscaler and tiered storage (SSD + HDD) to manage costs. Google’s Database Migration Service is free for same-engine migrations and now supports heterogeneous SQL Server-to-PostgreSQL migrations with Gemini-assisted conversion.

Oracle Cloud and IBM Cloud

Oracle and IBM have smaller cloud database portfolios but include some differentiated offerings.

Oracle Cloud Infrastructure

ServiceManagementLicensingMigration EffortRelative CostServerless
Autonomous DatabaseSelf-driving, fully managedBYOL or includedHighMedium-HigherYes
Base Database ServiceInfra-managed, DBA-controlledBYOL or includedHighMediumNo
MySQL HeatWaveFully managedOpen sourceMedium-HighLower-MediumNo
OCI PostgreSQLFully managedOpen sourceMedium-HighLowerNo
NoSQL Database CloudFully managedNo license feeVery HighLowerYes (on-demand)

Oracle’s Autonomous Database is genuinely self-managing โ€” it handles patching, tuning, and scaling without DBA intervention. MySQL HeatWave includes an integrated in-memory analytics engine and is available on OCI, AWS, and Azure. Oracle also runs natively within Azure and Google Cloud datacenters through multi-cloud partnerships.

IBM Cloud

ServiceManagementLicensingMigration EffortRelative CostServerless
Db2 on CloudFully managedProprietaryMediumMediumNo
Cloud Databases for PostgreSQLFully managedOpen sourceMedium-HighMediumNo
Cloud Databases for MongoDBFully managedProprietaryVery HighMedium-HighNo
Cloud Databases for EDBFully managedEDB licenseMedium-HighMedium-HighNo

IBM Db2 is one of the closer dialect matches to SQL Server among non-Microsoft relational databases, which may reduce stored procedure conversion effort compared to PostgreSQL or MySQL targets.

Multi-Cloud and Independent Platforms

Several database platforms run across multiple cloud providers, avoiding lock-in to any single vendor.

ServiceTypeLicensingMigration EffortRelative CostServerlessRuns On
SnowflakeData warehouseProprietaryMedium (analytics)MediumYesAWS, Azure, GCP
MongoDB AtlasDocument NoSQLProprietaryVery HighLower-MediumYes (Flex tier)AWS, Azure, GCP
CockroachDB CloudDistributed SQL (PG-compat)ProprietaryMedium-HighMediumYes (Basic tier)AWS, Azure, GCP
NeonServerless PostgreSQLOpen sourceMedium-HighVery LowYesAWS
PlanetScaleMySQL/PG (Vitess)ProprietaryMedium-HighLower-MediumNoAWS, GCP
TiDB CloudDistributed SQL (MySQL-compat)Open sourceMedium-HighLower-MediumYes (Starter)AWS, GCP
YugabyteDB AeonDistributed SQL (PG-compat)ProprietaryMedium-HighMedium-HigherNoAWS, GCP
AivenMulti-engine platformOpen sourceVariesLower-MediumNoAWS, Azure, GCP+
Crunchy BridgeManaged PostgreSQLOpen sourceMedium-HighLowerNoAWS, Azure, GCP
SupabasePostgreSQL + backendOpen sourceMedium-HighLowerPartialAWS

Snowflake is specifically an analytics platform, not an OLTP database โ€” it includes SnowConvert AI for automated T-SQL translation and a dedicated SQL Server migration guide. Neon offers true scale-to-zero serverless PostgreSQL with a dedicated SQL Server migration guide. CockroachDB and YugabyteDB are distributed SQL databases designed for global, multi-region deployments with strong consistency. MongoDB Atlas provides a Relational Migrator that can help convert SQL Server schemas to document models.

Cloud-Native and Consumption-Based Options

Some of these services were built from the ground up for the cloud โ€” no on-premises ancestor, no legacy architecture. Several offer consumption-based pricing where you pay only for what you use rather than provisioning fixed capacity. Here’s which ones meet that description:

ServiceProviderTypeBilling Model
Aurora Serverless v2AWSRelational (PostgreSQL/MySQL)Per ACU-hour, per second
Aurora DSQLAWSDistributed SQLPer DPU + storage
DynamoDBAWSNoSQL key-value/documentPer request + storage
Redshift ServerlessAWSData warehousePer RPU-hour, per second
Neptune ServerlessAWSGraphPer NCU-hour, per second
DocumentDB ServerlessAWSDocument (MongoDB-compatible)Per DCU-hour, per second
KeyspacesAWSWide-column (Cassandra-compatible)Per request + storage
ElastiCache ServerlessAWSIn-memory cachePer ECPU + GB-hours
Azure SQL DatabaseAzureRelational (SQL Server)Per vCore-second, auto-pause
Cosmos DBAzureMulti-model NoSQLPer RU consumed + storage
Synapse Serverless PoolsAzureData warehousePer TB processed
Azure Table StorageAzureKey-valuePer transaction + storage
BigQueryGoogleData warehousePer TiB scanned + storage
FirestoreGoogleDocument NoSQLPer operation + storage
Cloud SpannerGoogleGlobal relationalPer processing unit + storage
Oracle Autonomous DBOracleRelational (Oracle)Per ECPU-hour + storage
SnowflakeMulti-cloudData warehousePer credit consumed + storage
NeonMulti-cloudServerless PostgreSQLPer CU-hour + storage
CockroachDB BasicMulti-cloudDistributed SQLPer Request Unit + storage
MongoDB Atlas FlexMulti-cloudDocument NoSQLPer operation (capped)
TiDB Cloud StarterMulti-cloudDistributed SQLPer Request Unit + storage

What I Took Away

The landscape is enormous. What started as a straightforward question โ€” “should we move SQL Server to the cloud?” โ€” turns out to have dozens of possible answers depending on what you optimize for.

For organizations like mine that run on SQL Server today, the lowest-friction paths are clear. Lift-and-shift to a VM, or step up to a managed service that runs the same engine. On AWS, that’s RDS for SQL Server or RDS Custom. On Azure, it’s Azure SQL Managed Instance โ€” probably the single easiest managed migration path because Microsoft built it specifically for on-prem SQL Server workloads, with roughly 95% feature compatibility. On Google Cloud, it’s Cloud SQL for SQL Server.

But “lowest friction” and “best long-term fit” aren’t always the same thing. The cloud-native and consumption-based services are architecturally different โ€” many of them eliminate database administration entirely and scale automatically with demand. The tradeoff is migration effort. Moving from SQL Server to DynamoDB or Cosmos DB isn’t a migration โ€” it’s a re-architecture. Moving to Aurora PostgreSQL with Babelfish sits somewhere in between: you get a cloud-native engine with T-SQL compatibility that reduces โ€” but doesn’t eliminate โ€” the conversion work.

And sometimes the answer isn’t migrating at all โ€” it’s building the next thing differently. DynamoDB isn’t going to replace our SQL Server estate, but when I build a new web project from scratch, it’s where I start. No servers, no patching, no capacity planning. The right database depends on the workload, not on what you’ve always used.

I’m not making recommendations here. This is a map, not a GPS route. But having the full picture in one place makes the next conversation a lot more productive.

Sources