Choose an Azure Cosmos DB partition key you can live with
Think about query routing, data growth, and hot workloads before making a foundational modeling decision.
Explore Azure SQL, Cosmos DB, and Microsoft's analytics ecosystem, including Fabric and its data engineering tools.
Managed text, vector, and hybrid search for application retrieval.
Search enginesA distributed database platform where API, partitioning, and consistency choices shape the application.
NoSQL databasesManaged pipelines for moving and transforming data across supported systems.
Pipelines & streamingData lake capabilities built on Azure Blob Storage for analytical workloads.
Lakehouses & formatsManaged MySQL with Azure networking, backup, and availability options for application workloads.
Relational databasesManaged PostgreSQL with Azure networking, backup, and availability options.
Relational databasesMigration tooling for moving supported databases to Azure destinations.
Pipelines & streamingA managed event ingestion service with partitioned streams and consumer groups.
Pipelines & streamingA managed Redis service for applications that need fast data structure access.
Caching & in-memoryA managed SQL Server-based database service with database-level deployment choices.
Relational databasesA managed SQL instance with a broad set of SQL Server instance-level capabilities.
Relational databasesManaged stream processing for continuous queries over incoming events.
Pipelines & streamingAn Azure analytics workspace with SQL, Spark, and data integration capabilities.
Analytics & warehousesAn integrated Microsoft analytics platform with warehouse, lakehouse, and data integration workloads.
Analytics & warehousesThe logical data lake underlying Microsoft Fabric workloads.
Lakehouses & formatsMicrosoft's data governance, cataloging, and information protection capabilities.
Governance & BIThink about query routing, data growth, and hot workloads before making a foundational modeling decision.
Use application dependencies and operating requirements to choose a deployment model, not just a familiar product name.