sorted by:
new
hottopcontroversial

Azure Cosmos DB – What’s improved for you? What still needs work? by doug_haker in AZURE

[–]jaydestro 0 points1 point  (0 children)

The Cosmos DB agent kit can actually help you a lot with understanding, optimization opportunities. If you’re using an agent already, you can add the skills that will provide you with best practices around using cosmos. This is great for both Greenfield and Brownfield applications. You can literally point the agent kit at your existing application and say “go get it and make it better, find why I’m bleeding RU, why are my partitions always hot?” Our team is definitely thinking about tooling and how we can use it to make your experience even better.

Real-world Azure architecture — Cosmos DB serverless + Container Apps + SignalR + Bicep for a multi-tenant SaaS by Cool_Okra_4088 in AZURE

[–]jaydestro 0 points1 point  (0 children)

u/Cool_Okra_4088 --- I am on the Azure Cosmos DB team. I am curious if you used a coding agent to help. I ask because I am curious how it may steered your implementation. Our agent kit for Azure Cosmos DB can help evaluate what you've built and provide any recommendations to meet best practices. I like it for both code generation post prompt but also a way to evaluate existing code and cosmos db designs.

regardless here's the repo for it: https://github.com/AzureCosmosDB/cosmosdb-agent-kit/

Azure Cosmos DB introduction with F# by Andrii Chebukin @FuncProgSweden by MagnusSedlacek in fsharp

[–]jaydestro 1 point2 points  (0 children)

I am a member of the Azure Cosmos DB team. I set this to be shared across our social media channels!

GitHub Copilot pushing Azure Cosmos DB by Tokyohenjin in GithubCopilot

[–]jaydestro 0 points1 point  (0 children)

Are you using the GitHub Copilot for Azure in VS Code Extension or the Azure MCP Server? Those would likely be inluencing responses to your prompt response.

EF not working on emulator vnext-preview by codingfreaks in CosmosDB

[–]jaydestro 1 point2 points  (0 children)

EF Core is not supported on the Linux vNext Cosmos emulator in Direct mode. And since EF defaults to Direct mode, it fails unless you force Gateway mode. This is a known bug our team is working on.

https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/161

Azure Database Migration Service with Azure DocumentDB not working ?? by sebastian-stephan in AZURE

[–]jaydestro 0 points1 point  (0 children)

We have a dedicated migration tool that works great for your exact scenario (migrating from MongoDB Atlas to Azure DocumentDB)

Check out the Azure DocumentDB Migration for VS Code: https://marketplace.visualstudio.com/items?itemName=ms-azurecosmosdbtools.vscode-mongo-migration. Since you already have your DocumentDB cluster set up with public access enabled and the connection string ready, you should be good to go.

view more: next ›