Creating application based on Activiti

[galaxoft]

Hello,

I want to create a WEB based application which uses Activiti. The Activiti has a great API for persistence (DbSqlSession, CommandContext, etc.) and the workflow is needed for almost every function in my application (for 4-eyes principle and for other flows). Therefore I plan that every main function would be as a service (AccountService, LeadService, OpportunityService etc.) based on e.g. the IdentityService.
In this case all events will go through the Activiti Engine and in addition there wouldn’t be necessary two independent persistent layers to handle the SQL statements.
What is your opinion? Is this solution efficient (might be any performance issue)? Or the standalone application is the better approach (which only communicates with the Activiti via API).
Thank you for your suggestion in advance!

[jbarrez]

I think it's easier to keep it separated, and only use the Activiti to do what it can do best: driving processes.

Typically, i always sugget to keep your entities in it's own services and data storage, and reference them in the process.