I am looking at options for supporting multitenancy with OGM. The path I am considering is to support isolation at the cache level, similar to a schema isolation.

It looks like to do this, I would need a sessionFactory per tenant so I can isolate the metadata mapping per tenant and get unique cache names per Entity/Tenant, ala TenantId-Product, TenantId-Category, etc.

Would there be problems in using multiple sessionFactories for the same provider? Is there some other pattern I should consider?

Thanks,
--Rob

Hi,

Working with multiple factories should be fine, I suppose you'll have the burden of maintaining different (XML) mappings, though.

Hibernate ORM defines different means of multi-tenancy (see http://docs.jboss.org/hibernate/orm/5.1 ... ultitenacy) which essentially let you use the same mappings with a different database or schema per tenant.

I don't think that these options are supported yet in OGM, though. Could you try it out (probably you'd run into some JDBC-specific code paths) out and report back by creating a feature request in the OGM tracker (https://hibernate.atlassian.net/browse/OGM)?

It'll be an interesting exercise, as we currently work with a single DatastoreProvider instance (per session factory), whereas it would have to be one per tenant now.

Thanks,

--Gunnar