Workflow typically stores its state in very complex sql tables. If something goes wrong the tables are easily corrupted and then it is very hard to fix. (brittle) Also if the table design evolves, it is hard to migrate. This is my experience with Microsoft Workflow for Windows.
I believe an entity database will help when it becomes more feasible. On Tuesday, March 12, 2013 5:15:58 AM UTC-5, Ramos wrote: > > If i knew howto and have time i would create a workflow as a service. > This way i centralize all my rules for every app in a single app. > If i have 40 apps in my company it would be easy to manage all rules from > all apps. > > Is this a good way to go? > > > > 2013/3/12 Cliff Kachinske <[email protected] <javascript:>> > >> Workflow is not a winning proposition. If you're working with a small >> business they can't afford the t time it takes to do a decent job. If it's >> a large company they can afford a big time solution with all the bells and >> whistles. >> >> It's too ready to get tied up in the rocket science that the full time >> workflow specialists have created. >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "web2py-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
