We are running several ASP.NET applications (one per customer) based on our custom framework (which is just ASP.NET ) Each web application uses its own database (initial catalog in the word of connection string). We now want to add workflow capability to applications (respectively to our framework). Specific workflow will be the same for all applications, only some initial settings of each workflow can vary, e.g. In an application the e-mail will be sent to User X, but for other users, the Wi
The question is whether we can install a workflow engine (with a database of persistence) and share it for all workflows in all web applications.
If so, what workflow do the workflow in particular know which web application is related to? Should we find some application identifier somewhere in the workflow?
Thanks for the suggestions!
If all workflows are the same, then you can use a single workflow service service for each customer. And provide additional information such as email address such as startup parameters. However, if you think that you are going to zoom in to different clients, then I will create a separate host for each specific client. Of course you can always add it later
Comments
Post a Comment