Multiple Deployments Architecture

Q-Sensei Logs allows you to create multiple deployments. We see the following advantages of supporting multiple deployments:

  1. Flexibly & transparently distribute events across multiple deployments.
  2. With multiple deployments, analytical workloads can be distributed based on user groups and/or Kafka clusters.
    A typical scenario could be:
    • "Deployment 1" for Data Scientists, who use the deployment for Data Modeling and Exploratory Data Analysis.
    • "Deployment 2" for Business Intelligence users, who use data for predictive analysis and timely procurement.
    • "Deployment 3" for DevOps users, who use their deployment to monitor events from the AWS Cloud Infrastructure and configure alerts.
  3. Each deployment is isolated from one another and does not affect the performance of the other deployments.


Personal Account

  • With Q-Sensei Logs SaaS, you get the highest possible level of tenant isolation.
  • During onboarding you will specify the AWS region where your account should be created and your personal domain name.
  • We create a personal domain for you to access the Q-Sensei Logs application. If you chose example as your domain name then the Q-Sensei Logs application can be accessed at


  • With multiple deployments there is a need for managing these deployments from one place. For a detailed documentation on the available functionalities, read the section on Manager UI.


As explained for single deployments, each deployment has its own:

  • Events Collection Tier,
  • API Gateway,
  • Events Ingestion/Indexing Tier, and 
  • Analytical Search Tier.
Was this article helpful?
0 out of 0 found this helpful