Play 2.3+ Multi-tenancy (Schema/DB per tenant) example

[Nicolaas Frederick Huysamen]

We are evaluating using Play for a new application, but one requirement is that we have shema (or db) per tenant multi-tenancy. Tenants are created dynamically (by creating their schema from a template). Are there any good examples of achieving this in Play? During the request we are able to figure out the tenant from the request headers, so a simple stateless approach will work great.

Thanks

[Ian Rae]

Play works well with Flyway, which does schema creation (and migration) programmatically.

   http://flywaydb.org/

[Nicolaas Frederick Huysamen]

Not quite what I was asking about though. I am interested in knowing how (or if) Play can do multi-tenancy with db/schema per tenant from a single app.

[Earle Nietzel]

Hi Nick,

Sounds like unified access to your tenant datasources is what your looking for.

Apache Spark might be a fit for your design..

https://spark.apache.org/

[Alberto Souza]

There is nothing out of the box. Probably you will need to create an Action composition to decide which tenant is accessing your application and create the SessionFactory/EntityManagerFactory/WhateEverFactory based on that. Hibernate 4 has support for the schema approach. Here is the link => http://docs.jboss.org/hibernate/orm/4.2/devguide/en-US/html/ch16.html#d5e4771

Alberto Souza

www.caelum.com.br
www.leanpub.com/playframeworknapratica
www.alots.wordpress.com/

[Rajendra Prasad Gujja]

This is a little old post, but it may benefit other users like me.

I have put together an example on how Play + JPA (Hibernate) works to achieve multi-tenancy. It supports schema/database per tenant with the support of a common database which will have "common to all tenants" information.

Here is the link https://github.com/rajendrag/play-jpa-multitenant

Thanks,

Raj.

[Felipe Alfaville]

https://github.com/kcthota/play-ebean-multitenant-example