A few CosmosDB query limitations

I’ve been working quite a bit with Cosmos DB since it was release in Private Preview (see my first article about it back in September 2014 as a battle scar).

It has come a long way.

From DocumentDB, the NoSQL document-oriented DB to Cosmos DB, the Globally distributed...

Setup for populating Cosmos DB with random data using Logic Apps

We recently published an article about Cosmos DB Performance with Geospatial Data.

In this article, we’re going to explain how to setup the environment in order to run those performance test.

More importantly, we believe this article is interesting on its own as it shows how to use...

How to Create a Logic App Connector in an ARM Template

I wanted to automate the performance test setup we discussed in the last article.  This includes a Logic App calling into a Cosmos DB stored procedure.

Logic App uses connectors when connecting to other services, either within or outside of Azure.  Now how do we...

Cosmos DB Performance with Geospatial Data

Time for some performance tests on Cosmos DB around Geospatial coordinates!

Let’s hurt the service and see where it shines, where it has a hard time and how scaling it (i.e. increasing Request Units or RUs) helps.

We’ll publish an how-to create the same setup in a future article...

Invoking a Stored Procedure from a partitioned CosmosDB collection from Logic Apps

I struggled a little to make that work, so I thought I would share the learning in order to accelerate your future endeavour.

I was looking at a way to populate a CosmosDB quickly with random data.

Stored Procedures came to mind since they would skip client-server latency.  We can call a stored procedure creating hundreds of documents with random...