Persistence service with more than one database

Oct 26, 2007 at 2:36 PM

I have integrated this software in my project and I'm using the persistence service without any problem. But now I have a new requirement: my persistence service needs to work with more than one database!!

Considering I'm only using the persistence service, do you think it could be a good idea? Do you recommend doing something like that?

Thanks in advance,

Oct 29, 2007 at 6:22 PM
Hi Francesc,

Can you explain your scenario a little more? Is it along the lines of this post:

If so I'd look at something like Oracle RAC or SQL Server clusters as you're really looking at database resilience which may not be best solved at application level.

If you genuinely want to persist workflow to more than one database then this needs a bit more consideration. A custom persistence service could potentially write to more than one database but what happens when you come to read the data back out to rehydrate a workflow instance? Which persistence store is considered 'correct', etc.?