While I agree on limitation of indexes - you get 3 - table name, partition key and row key, you can 'nicely repeat data' by embedding it via serialization. I p

While I agree on limitation of indexes - you get 3 - table name, partition key and row key, you can 'nicely repeat data' by embedding it via serialization. I ported my db from mongo over to storage tables. I was embedding data, so I didn't have to do two lookups, and when I moved over to storage tables, I wanted the same thing, so simply serialized via protobuf - works a treat.