Gratuitous nostalgia demands to know about the first time the Songhay System published interest in Windows Azure: that was in 2010. Then, in 2012, a massive moment in Internet history is declared with the introduction of Azure Web Sites. So far nothing has been posted about Azure Table Storage (ATS) and, based on what will be reported here, it’s understandable. The Songhay System strategy for ATS is locked in the Silverlight era: the library,
Songhay.Cloud.Entities, shows intent to support RIA Services—as declared forcefully here in 2012. Like everything in the universe, this is going to change. The following is what we have at the moment.
First of all, there is no real Partition Key design strategy. More on this later… (?)
Songhay.Cloud.Entities is built on these packages:
<package id="Microsoft.WindowsAzure.ConfigurationManager" version="22.214.171.124" targetFramework="net45" /> <package id="RIAServices.WindowsAzure" version="4.1.60730.0" targetFramework="net40" /> <package id="WindowsAzure.Storage" version="126.96.36.199" targetFramework="net45" />
Because of the versions used above, the ‘old way’ (the “Data Context” way) of working with ATS is in effect. For example, the old way of retrieving a document:
var tableClient = account.CreateCloudTableClient(); var context = tableClient.GetDataServiceContext(); var query = context.CreateQuery<TableStorageDocument>("TableStorageDocument"); var document = query .Where(i => i.PartitionKey == partitionKey) .Where(i => i.RowKey == rowKey) .FirstOrDefault();
Here would be the ‘new’ (verbose-but-systematically-honest) way:
var tableClient = account.CreateCloudTableClient(); var tableReference = tableClient.GetTableReference("TableStorageDocument"); var operation = TableOperation.Retrieve<TableStorageDocument>(partitionKey, rowKey); var operationResult = tableReference.Execute(operation); if(operationResult == null) throw new NullReferenceException("The expected result is not here."); var document = operationResult.Result as TableStorageDocument;
Note how the new way (Windows Azure SDK v2.x) is removing any LINQ-related, misleading suggestions of query flexibility.
And then there is the REST-based way, considered by many the only way. But the snag (for me) is getting past how authentication is done for REST-based operations. There seems to be buzz about “Shared Key” and “Shared Key Lite”—stuff I’ve no time to grasp today…
The ‘old,’ 2010 of approaching Azure Table Storage…
The ‘new,’ 2014 way of handling ATS…
This link came from search result during an experiment.
MSDN documentation on the REST-based way to ATS.
“The Table service requires that each request be authenticated. Both Shared Key and Shared Key Lite authentication are supported. Shared Key authentication is more secure and is recommended for requests made against the Table service using the REST API.”
“The trick I learned to handle this came from this whitepaper which uses a
“The Azure storage services support both HTTP and HTTPS; however, using HTTPS is highly recommended.”
“Kyle has several blog posts [explaining] how to use Windows Azure Table Storage (WATS) Domain Service, the support of which comes from WCF RIA Services Toolkit.”
“The owner has unlisted this package. This could mean that the package is deprecated or shouldn’t be used anymore. …Includes SOAP and JSON Endpoints, EntityFramework 4.1 support, jQuery Client, T4 Code Generation, and the Windows Azure Table Storage DomainService.”
“The difference between Jim’s approach and what I’ll show here are the steps we take to integrate with existing
“The partition key is being used for the load balance of the Azure OS and the group entity transaction. As you know in the cloud you will never know which machine is hosting your application and your data. It could be moving based on the transaction weight and the number of the requests. If the Azure OS found that there are many requests connect to your Book entities with the partition key equals ‘Novel’ it will move them to another idle machine to increase the performance. So when choosing the partition key for your entities you need to make sure they [indicate] the category or [group] information so that the Azure OS can perform the load balance as you wish.”
“Windows Azure Table storage has minimal support for LINQ queries. They support a few key operations, but a majority of the operators are unsupported.”
“At first, working with Windows Azure Table Storage may seem a little unwieldy due to assumptions made by relating “table storage” to a SQL database. The use of ‘table’ in the name doesn’t help. When thinking about Windows Azure Table Storage, I suggest that you think of it as object storage.”
“If you’re looking for fast, highly flexible data storage with high redundancy and no need for the rigor of a relational database, then AWS SimpleDB is a nice choice.”
“Did you know that data stored in Windows Azure Table storage can be accessed through an OData feed? Does that question even make sense to you? If you answered no to either of those questions and you are interested in learning more, then read on. In this post I’ll show you how to use the OData SDK for PHP to retrieve, insert, update, and delete data stored in Windows Azure Table storage.”