Skip to end of metadata
Go to start of metadata

This page contains topics supporting ongoing discussion at dev@syncope.apache.org.

Tracked as SYNCOPE-652.

The purpose of this new feature is to provide the possibility of defining separated "containers" for all entities currently managed by Syncope in order to allow the execution in multitenant environments.

Additional requirements:

  1. Physical separation: data for different domains MUST reside on different database instances
  2. Heterogeneity: data for different domains MAY be hosted on different database engines (domain A on MySQL, domain B on Oracle, ...)

Entity changes

Each and every entity will need to refer to a new Domain entity; all relationships among entities will require to be in the same domain.

The idea is to empower OpenJPA slices to achieve physical separation of SQL tables related to different domains (each domain will require a dedicated slice). An additional slice, the master slice, will always be available for working without domains or to hold domain information related to all domains.

The idea is to allow the definition of multiple EntityManagerFactory instances via Spring's LocalContainerEntityManagerFactoryBean: being each EntityManagerFactory related to a different DataSource and DBDictionary, this will permit to achieve physical separation of SQL tables related to different domains.

REST API changes

Each REST endpoint will check for the availability of a new HTTP header X-Syncope-Domain containing the domain in which the requested operation will take place; absence of such header will imply that operation is to be performed on master domain.

  • No labels

1 Comment

  1. FYI: OpenJPA slices were ditched because they are actually a non-standard mechanism built on top of JPA.