Workflow Database Documentation
Audience
Backend engineers, database engineers, QA, support, security engineers, solution architects and implementation partners.
Overview
This section documents the verified EF Core persistence model owned by Workflow Service. It does not provide connection details, operational commands or executable database statements.
Summary
Workflow persistence is Foundation/Transitional. One runtime DbContext owns a dedicated schema and 11 entity sets. Definition and instance aggregates use cascade relationships; audit, timeline, processed-event and outbox records share the same context.
One initial migration and one model snapshot exist. Development startup can migrate and seed five published definitions. No retention worker, concurrency token, database-specific test project or production migration procedure was found.
Documentation map
Start with database overview, persistence architecture and DbContext inventory. Entity pages cover definitions, versions, steps, conditions, instances, tasks, actions, audit/timeline, outbox and processed events.
Engineering references cover tenant isolation, mappings, relationships, indexes/constraints, value conversions, queries, transactions, concurrency, migrations, seeding, retention, testing, schema, limitations and source map.
Requires Confirmation
Production migration ownership, tenant trust, outbox/processed-event isolation, retention, concurrency policy, backup/recovery and database test ownership require confirmation.
Source References
microservices/src/workflow-service/Infrastructure/WorkflowDbContext.csmicroservices/src/workflow-service/Infrastructure/Persistence.csmicroservices/src/workflow-service/Infrastructure/Migrations/20260706165438_InitialWorkflowSchema.csmicroservices/src/workflow-service/Infrastructure/DevelopmentSeeder.cs
Related Articles
See Also
Keywords
Workflow database, EF Core, Workflow schema.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20