Multi tenancy support in camunda

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Won't Fix
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: engine

      can we have process engine, process definition and database schema for each tenant. i.e., per tenant providing separate resources. is this good practice?

      For example:

      Tenant 'A' -> ProcessEngine A, Processdefintion A, DatabaseSchema A
      Tenant 'B' -> ProcessEngine B, Processdefintion B, DatabaseSchema B

      Below are my few understandings about camunda multi-tenancy support:

      1. Table per tenant in same schema
      2. Tenant identifier(discriminator column) at table level for each record in same schema
      3. Shared process engine and shared process definition for all tenants (tenants will be identified through tenant identifier – follows either point a or b)
      4. Deployment per tenant (Shared process engine and process definition per each tenants)
      5. Process Engine per tenant(tenants will have own deployment) – different database schema per tenant.

            Assignee:
            Unassigned
            Reporter:
            Aravindh Ravi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: