[FALCON-476] Introduce database to persist falcon materialized workflow status in workflow engine

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.6
• Component/s: messaging
• Labels: persistence
• Assignee: Unassigned
• Reporter: Venkatesh Seetharam
• Created: 17/Jun/14 08:52
• Updated: 08/Sep/14 21:29

Description

Introduce a relational DB for storing state of the workflows materialized by Falcon in the workflow engine. APIs should use the state in the DB instead of going to the workflow engine for every request enhancing the performace requirements of a user dashboard.

Issue Links

• is blocked by: FALCON-327 Simplify message passing framework
• is related to: FALCON-469 Enhance REST API to drive interactive user dashboard

Sub-Tasks

• Persist workflow job end notifications into a database for driving the dashboard use cases: Open
• Convert existing read-only REST APIs to use the state in the DB instead of going to workflow engine: Open
• Add health checks for DB with a validation query: Open
• Introduce liquibase for database creation and migration with capability to rollback: Open