Azure DocumentDB Users in a multi tenant application -


i playing around azure document db because planning create multi tenant application.

for multi tenant application, idea create 1 db user per tenant. gives me advantage tenant data separated: when creating document, permission added tenant user. (read/write) means when querying, data scoped current tenant.

i playing around 1 db user per end-user. gives me lot of overhead manage security on documents. when user x tenant z adds document, users tenant z need updated permissions document. seems unfeasible.

is assumption correct? or suggest approach this? there downside approach?

for our multi-tenant solution chose not use documentdb's controls @ , of our authorization in middle tier because wanted predicate based , different per tenant. said, approach of using documentdb's authorization capabilities @ tenant level makes sense. give tenants added assurance other tenants can't see data.

my 1 thought if have cross-tenant functionality (maybe in form of tenant groups) break model may want consider that.

i assume tenants hundreds , users thousands whatever are, should confirm documentdb authorization capability scales level. maybe 1 of documentdb product managers monitor can chime in?


Comments

Popular posts from this blog

php - How to add and update images or image url in Volusion using Volusion API -

javascript - jQuery UI Splitter/Resizable for unlimited amount of columns -

javascript - IE9 error '$'is not defined -