I've been reading the forum posts on multi-tenancy and I have what might be silly question: What about running a single Tomcat server per tenant that, in turn, connects to a distinct database?
I've run two dozen Tomcat servers on the same physical machine in the past. Activiti appears to have a very low memory usage profile. On a Small, Reserved AWS instance, one could probably handle 25 tenants running 25 Tomcat servers.
Sure, this is off course feasible, if you approach activiti using the REST-api. if you have a single point of access (for all tenants- that uses the Java API, that's not possible. 5.15 contains tenancy-capabilities, having tenant-specific deployments, process-definitions, …
Since we will be accessing the engine from an ASP.NET server, REST is the only way we'll be going. We're developing a SPA (Single-Page Application) using Durandal against Web API 2.0 and SignalR server-side.
It's great to hear that 5.15 will offer multi-tenancy. Any idea on the time frame? We have a lot of other work to do and could easily triage the workflow portion in anticipation of 5.15.