We used Azure table storage as NoSQL data storage for quite a time and got some experience which may be useful to share with community. First of all I want to say that I like Azure table storage: it is very simple to use (there are different SDKs), flexible with it's dynamic data schema for tables (although this must be a common thing in NoSQL world), fast (if you use it correctly and avoid full table scan scenarios) and last but not least - it is very cheap.
However at the same time it has number of cons which may be significant depending on amount of data you need to process and performance which you need to achieve. I collected them in the following table:
| Cons | Comments |
| No LIKE operator | Can't perform search by sub string. Need to introduce complex data duplication patterns with different PartitionKey/RowKey for avoiding full table scan and performance issues |
| Only 2 system indexed columns (PartitionKey/RowKey) without possibility to add own indexes | Can't add custom indexed fields for improving queries performance |
| No full pagination support on API level | There is possibility to limit returned resultset size, but no possibility to skip number of rows |
| No native backup options | There are 3rd party (including open source) solutions which can be used but no built-in support from MS |
Like I said I personally like Azure table storage. But due to these cons you may also consider other options for data storage e.g. Azure CosmosDB which is more expensive but also more powerful at the same time.
No comments:
Post a Comment