This post has been republished via RSS; it originally appeared at: Azure Data Explorer Blog articles.
I often get the question from customers who are using Azure Data Explorer (ADX) as an analytical back end for their solution "What is your guidance on how to leverage ADX in a multi-tenant architecture"?
We recently released a new documentation article titled How to architect a multi-tenant solution with Azure Data Explorer answering that very question!
This topic is quite rich. For a lot of customer solutions, having an ADX cluster per end-customer doesn't make sense from a cost and management perspective, but packing multiple end-customers (or tenants) within a cluster opens up a lot of questions about security, performance isolation, manageability and customization possibility. Those in turns have many facets.
This new article explores 3 typical architectures and their characteristics:
- One tenant per database
- One database for many tenants
- One tenant per table in a single database
Hopefully this article will equip you to weigh the pros and cons of each architecture within your solution context and requirements and enables you to choose the best one for you.
Read How to architect a multi-tenant solution with Azure Data Explorer