Really awesome stuff! Can I deploy it using an ARM template now, or do I have to wait for that? (or with pulumi that I'm using, but if it is in arm it will be in pulumi shortly)
How can we even add this in local postgreSQL? Scripts in docs doesn't work for Ubuntu nor Fedora. I can use single node with Docker. Also since this is an extension, could we use this with timescaledb? If we can't use this locally, then at least there should be developer version that is affordable.
While the implementations of different Cosmos DB flavors could be different; the ideas, direction, IP, etc. are aligned. Just like other Cosmos DB APIs, Azure Cosmos DB for PostgreSQL is a seamlessly scale-out, globally distributed modern, cloud-native database service.
@@aamederen does it apply the concepts like partition key and throughput models similarly or differently when compared to the regular cosmosdb? (tebrikler :) )
@@hodor2704 The underlying concepts are similar but the terms might be different. For example, we use the term "shard key" for dividing the data. The throughput model is different for CDPG, you provision a server group by specifying the number of nodes, vcores and storage options. (tesekkurler :))
May I know what is the main difference here in "Azure cosmosDB for Postgresql"? when compared to "Hyperscale - Azure Postgres deployment mode". I also observed it is removed from deployment model too. Is that means both are same or any extra additions to the "Azure CosmosDB for postgresql"?
The Azure CosmosDB for PostgreSQL is the new name and home for the Azure Database for PostgreSQL - Hyperscale (Citus) product. The existing PG Hyperscale instances will be moved under the Cosmos flag. There are no regressions or major behavioral changes, apart from the new features.
Solid content and demo! Truly enjoyed this
Thank you!
Exciting stuff !
Really awesome stuff! Can I deploy it using an ARM template now, or do I have to wait for that? (or with pulumi that I'm using, but if it is in arm it will be in pulumi shortly)
How do I use the azure storage extension? And can I also use that extension in a local database?
Can we use EF Core in a .NET App to communicate with the CosmosDB PostgresSQL provider?
How can we even add this in local postgreSQL? Scripts in docs doesn't work for Ubuntu nor Fedora. I can use single node with Docker. Also since this is an extension, could we use this with timescaledb? If we can't use this locally, then at least there should be developer version that is affordable.
Is it just using the name 'cosmos db' or does this actually have something to do with Cosmos DB?
While the implementations of different Cosmos DB flavors could be different; the ideas, direction, IP, etc. are aligned. Just like other Cosmos DB APIs, Azure Cosmos DB for PostgreSQL is a seamlessly scale-out, globally distributed modern, cloud-native database service.
@@aamederen does it apply the concepts like partition key and throughput models similarly or differently when compared to the regular cosmosdb? (tebrikler :) )
@@hodor2704 The underlying concepts are similar but the terms might be different. For example, we use the term "shard key" for dividing the data. The throughput model is different for CDPG, you provision a server group by specifying the number of nodes, vcores and storage options. (tesekkurler :))
Touché👌
May I know what is the main difference here in "Azure cosmosDB for Postgresql"? when compared to "Hyperscale - Azure Postgres deployment mode". I also observed it is removed from deployment model too. Is that means both are same or any extra additions to the "Azure CosmosDB for postgresql"?
The Azure CosmosDB for PostgreSQL is the new name and home for the Azure Database for PostgreSQL - Hyperscale (Citus) product. The existing PG Hyperscale instances will be moved under the Cosmos flag. There are no regressions or major behavioral changes, apart from the new features.
Super cool but man is it expensive! @_@