This is a quick start on using the Cosmos DB Bindings with HTTP Triggers on Isolated Runtime Azure Functions.

I threw this together because all the Isolated Runtime examples were using Queues which don't require the extra output that HTTP Triggers require to provide a proper return status.


Today just wanted to highlight a simple Azure SQL and Azure Queue example that uses Azure Functions to schedule and move data to SQL Azure from a REST API in parallel. It shows a heavy use of bindings to keep the code very tight while being highly functional. My favorite part is the SchedulePokemonQueue function, in 11 lines of code it gets all of the data from the SQL DB and drops them onto the queue to be processed with essentially just some scaffolding and a for loop.