Designing a Workflow Engine Database Part 8: Complete Schema and Shortcomings
Let's take a look at our final database design for our Workflow Engine and discuss some shortcomings of this design (Part 8 of 8).
Workflow Engine
An eight-part series on designing a workflow engine database.
Designing a Workflow Engine Database Part 7: Request Actions
The last piece of schema is Request Actions, which allow us to specify which Actions can be performed at any given time. (Part 7 of 8).
Designing a Workflow Engine Database Part 6: Groups and Targets
Let's design Groups and Targets for our Workflow Engine and wire them up to Actions and Activites (Part 6 of 8).
Designing a Workflow Engine Database Part 5: Actions and Activities
Let's design the database tables that represent process Actions and Activites for our Workflow Engine (Part 5 of 8)
Designing a Workflow Engine Database Part 4: States and Transitions
Let's design what States and Transitions mean for our Workflow Engine database (Part 4 of 8).
Designing a Workflow Engine Database Part 3: Request Details and Data
What makes a Request, and how can we store data that is unique to each Process? Find out in this post! (Part 3 of 8)
Designing a Workflow Engine Database
What is a Workflow Engine, and what does it do? Let's find out and set off on a Database Design adventure (Part 1 of 8).
C#, .NET, Web Tech, The Catch Block, Blazor, MVC, and more!
You've successfully subscribed to Exception Not Found
Welcome back! You've successfully signed in.
Great! You've successfully signed up.
Your link has expired
Success! Your account is fully activated, you now have access to all content.
