To articulate the business process in a workflow environment, there are some interesting proposals out there:
Camunda: C# library. It works well with .Net Core 3.x
Elsa: C# library
WorkFlow Engine: C# Library. It works well with .Net Core 3.x
Hangfire: Is all about executing jobs on servers (shceduled jobs). Has a web-based dashbord. It can run on a server.
Microsoft Dynamics 365 Supply Chain Management: Difficult to learn; high learning curve, and you have to pay a subscription fee every month for it.
Problem with existing solutions
Must of them are great. But the problem is you have to choose one... and to be able to choose one properly, you may have to test all of them, and to do that you are going to need to learn about them. The learning curve will high, so the whole process will take some time eventually.
If you're in a rush, which happens very often in software development, and if you are an experienced coder, probably you will provide yourself a solution from your own industry.
WorkFlows are a crucial part of the business process. So you have to be careful about what dependencias you are going to stabish on the company codebase. So you're probably going to want to partner with a company that will assure you of long-term support. Many small independent developers are brilliant, but they can't guarantee that.
Please investigate all these alternatives and have your say. Any contribution will be very appreciated.
Exsisting Solutions
To articulate the business process in a workflow environment, there are some interesting proposals out there:
Problem with existing solutions
Must of them are great. But the problem is you have to choose one... and to be able to choose one properly, you may have to test all of them, and to do that you are going to need to learn about them. The learning curve will high, so the whole process will take some time eventually.
If you're in a rush, which happens very often in software development, and if you are an experienced coder, probably you will provide yourself a solution from your own industry.
WorkFlows are a crucial part of the business process. So you have to be careful about what dependencias you are going to stabish on the company codebase. So you're probably going to want to partner with a company that will assure you of long-term support. Many small independent developers are brilliant, but they can't guarantee that.
Please investigate all these alternatives and have your say. Any contribution will be very appreciated.