Rob Caron

@GermanKuber: Captions fixed. Thanks for letting us know!

@GermanKuber: Captions fixed. Thanks for letting us know.

You can find the sample code in this GitHub repository: 

https://github.com/Azure/azure-documentdb-dotnet/tree/master/samples/request-units

@Rohit:

To replicate the above demo, you need a setup like the following

TwitterProducer --> Kafka <-- Storm Consumer

For a TwitterProducer, you can use a simple spark notebook as detailed below
(doc for the setup)

https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-apache-kafka-spark-structured-streaming

(notebook for the actual producer)
https://github.com/Azure-Samples/hdinsight-spark-kafka-structured-streaming

Once you have this working, you can use Storm to consume the messages from Kafka as shown here
https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-apache-storm-with-kafka

Let us know if you have more questions.

@mjda: Touché. See: Azure Germany or Azure China. 

@Kinser: Azure CLI 2.0 is comparable to using Azure cmdlets in PowerShell. Use the one that goes best with your choice of command shells, so just preference for the most part.

The delay in posting the bits on Microsoft Downloads is not part of a nefarious plan. On MSDN Subscriber Downloads, we can post a single file containing the ISO image rather easily. To post that download on Microsoft Downloads, we have to split it into a multi-volume self-extracting file, reverse the process and ensure the self-extraction works correctly, publish these files through a system that is optimized for much smaller download files, and then we usually download the files ourselves and test them again for integrity. We're commited to have these downloads up on Microsoft Downloads ASAP.

The ISOs are coming very soon for Microsoft Downloads, and they are already showing up on MSDN Subscriber Downloads (see: Visual Studio Code Name "Orcas" Beta 1 for MSDN Subscribers).