|
|
|
| There's more than one way to do things | |
| PerlMonks |
Re: Design question: handling hundreds of state machines in a Web contextby RichardK (Parson) |
| on Jan 02, 2013 at 18:34 UTC ( #1011330=note: print w/replies, xml ) | Need Help?? |
|
I agree with Corion, store your state in an ACID database then state changes can happen in transactions. I'd choose postgresql but YMMV. From what you've described, I don't think you'd get much advantage from a queueing system but without seeing a full & detailed spec it's difficult to tell :)
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||