In the previous post I have described the second week of "Data Structures and Algorithms" course on Coursera. In this post I am going to cover the third week of that course.
In the previous post I described the first week of "Data Structures and Algorithms" course on coursera. In this post I am going to describe the second week.
In the previous posts I have described Azure Queue and provided small usage examples. In this post I am going to show how Azure Table service can be managed from Powershell. Azure Table service is a service that stores structured NoSQL data in the cloud. It is a key/attribute store with no schema. Also, it is worth to mention that it costs much less that SQL Database for similar volumes of data. You can use the Table service to store and query huge sets of structured, non-relational data, and your tables will scale as demand increases. There is a good post Working with 154 million records on Azure Table Storage – the story of “Have I been pwned?” about Azure Table service that everyone should read.
We all know that algorithms are everywhere. I studied algorithms and data structures in the university, but I don't know them good enough. So I decided to enroll into Data Structures and Algorithms, University of California, San Diego & Higher School of Economics on Coursera. I hope it will be a good experience and lots of fun. I already know half of the material and used some of the advanced algorithms and data structures during my study in university, but I still have lots of gaps.
In previous post I have described stored access policies and provided basic code samples. In this post I am going to discuss another topic - attributes and metadata. Attributes is simple properties, metadata for a queue is stored as name-value pairs.
In the previous post I described how
PopReceipt can be used and provided simple examples. In this post I will continue to work with Azure Storage Queue Service. I am going to describe an important parameter