Ah yup, that makes a lot more sense. I can imagine how fun that might be trying to do through EF. It sounds like a workflow engine. I'm picturing one table tha

Ah yup, that makes a lot more sense. I can imagine how fun that might be trying to do through EF. It sounds like a workflow engine. I'm picturing one table that is very generic that tracks "this job id, this workflow type, this stage in workflow, this entity, this state of the entity" and a single job has multiple of those entries over the lifetime of that job execution and the JSON blob is the current state of things, so that you don't have to go and recompute that. Yeah, it seems like a reasonable choice. What sticks out to me in a scenario like that is a good CQRS implementation. The write side of it pumps in the history of the job execution, then denormalizers run to project that into a shape amenable to being read by the application.