is the notion of a Table required at all in Azure Table service? -
i working azure table services. ask whether azure internals care notion of table @ all?
making things fast largely depend on partition key , row key. tables not containers or grouping of entities because there no limit on number of tables can create. total storage size tied storage account.
so table notion people transition rdbms land or serve purpose internally? can applications single table design without worrying performance? after all, if table tag may include part of partition key.
edit
to give example, table partition keys cassandra rows , table rows cassandra columns. okay treat storage big bucket of key(rowkey)-value pairs. partition keys sharding mechanism. table comes across "labeling" notion.
you can have entities in single azure table storage , optimum performance thoughtfully choosing right partition key , row key combination, imho time better have related entities each in separate table easy manageable ( developer perspective) . know part of application hitting table.
you may want view recorded session discusses best practices , internals. windows azure storage: what’s coming, best practices, , internals
Comments
Post a Comment