Wishing to contribute from multitenancy angle

[iramkumar]

I just published a paper on graphical financial risk modeling and used Activiti as the engine for experiments. I am very happy with Activiti and the ease of use, clean documentation and next generation concepts it has integrated.

I wish to contribute to Activiti from a multi-tenancy standpoint that was the future work in my paper. There is also the fact that cloud is making multi-tenancy an important feature.

There is an important paper that breaks down multi-tenancy architectural concerns as
Extensibility
Persistency
QoS Differentiation
Performance Isolation
Affinity (CPU/Node)

I am basing my work on that. On which angle should I contribute to Activiti. I know there is a multitenancy feature where you can set a tenant ID with isolated signalling. But apart from that are there any ideas for say dynamic process creation, isolating tenant process performance etc.

I am a newbie so please point out the area and module and I would love to contribute.

[trademak]

Can you share more details about the multi tenancy functionality you are thinking about?

Best regards,

[iramkumar]

Mult-tenancy refers to the ability to run tenants getting a single view of a code shared between multiple tenants. Extensibility is an important aspect in which Activiti can fit very well. It already has a tenantID when starting processes which have same definition or definitions with modifications.

At present, I am not all sure what are the things of any priority for Activiti. For example, can you pass QoS parameters into processes? Can you signal processes to slow down their  speed of execution? Can you signal different persistence mechanisms to processes (There is work on NoSQL Activiti also) These are some vague ideas. If there are pointed extensions Activiti wants to do then I can take it forward.

My short paper on how I used Activiti  is here.

https://drive.google.com/file/d/0BwrNg-893yAJSzVEakE5MnZGcFU/view?usp=sharing

[trademak]

How would that work, passing QoS parameters into processes? Could you give a practical example?
What would be the purpose of slowing down the speed of execution of a specific process instance?
Different persistence mechanisms would work for dynamically changing the history level for a specific process instance. The NoSQL Activiti work was just a prototype for now.
Thanks for sharing the paper. I'm still figuring out what kind of multi tenancy functionality you are thinking about.

Best regards,

[iramkumar]

How would that work, passing QoS parameters into processes? Could you give a practical example?
For example I am in financial risk when a large number of rules of executed by a rule engine  to give a final result on the amount of money to be held. If rule depth was a parameter we can give different answers that are approximate or exact to that extent. This could probably be passed as a hash map variable as it is done right now. But a framework would be even better.

What would be the purpose of slowing down the speed of execution of a specific process instance?
In Multi-tenancy, in methodology you allocate quotas to different clients. If some one exceeds the quota we slow them down.


I am only looking as of now to contribute to open areas. Even I am not very sure how to do the same.