topic In memory database in Alfresco Archive

In memory database

snowch1 — Wed, 19 Jan 2011 18:45:44 GMT

I need a lightweight workflow solution for short lived sessions (< 10 mins). I don't want to persist the workflow sessions in a database. Is Activiti suitable for this type of solution, perhaps using hsql?Many thanks in advance,Chris

Re: In memory database

frederikherema1 — Thu, 20 Jan 2011 06:45:46 GMT

Hi,

Default database used by activiti is H2. If you use the org.activiti.engine.impl.cfg.StandaloneInMemProcessEngineConfiguration to configure activiti, it uses an in-memory database ( JDBC-url: jdbc:h2:mem:activiti).

The same configuration is used when we run our engine JUnit test-suites, which run very fast so Activiti is no doubt suitable for your needs.

Re: In memory database

wbenass — Wed, 24 Oct 2012 19:42:34 GMT

Reading that H2 is not prod ready due to table locking but then later read that can be changed. Is there an option with Activiti to have the DB in memory in a production scenerio with lots of concurrency? H2? Other?

Re: In memory database

jbarrez — Thu, 25 Oct 2012 08:26:03 GMT

production and in-memory are two things that don't go well together ….

Re: In memory database

wbenass — Fri, 16 Nov 2012 17:18:45 GMT

Thanks for the reply. I would not jump to conclusions with respect to that. I can think of more than 1 instance where use of an in-memory database is superior to the alternative. We have a need for a **lightweight** process orchestration whose state dies along with the runtime, minimal maintenance, etc. So I would ask my question again…is there an Activiti configuration that is suitable for production using the in-memory database?

Re: In memory database

jbarrez — Fri, 16 Nov 2012 18:47:16 GMT

Activiti is only tested with H2. But as far as I know, any of the popular in memory databases (Derby, HSQL, …) use table locking.