Summary - Extending Conductor - Githubissues

kymr / conductor

Conductor is a microservices orchestration engine - https://netflix.github.io/conductor/

Apache License 2.0

0 stars 0 forks source link

Summary - Extending Conductor #10

Closed kymr closed 6 years ago

kymr commented 6 years ago

Link

https://netflix.github.io/conductor/extend/

kymr commented 6 years ago

Backend

Conductor provides a pluggable backend. The current implementation uses Dynomite.

There are 4 interfaces that needs to be implemented for each backend

//Store for workflow and task definitions
com.netflix.conductor.dao.MetadataDAO

//Store for workflow executions
com.netflix.conductor.dao.ExecutionDAO

//Index for workflow executions
com.netflix.conductor.dao.IndexDAO

//Queue provider for tasks
com.netflix.conductor.dao.QueueDAO

It is possible to mix and match different implementation for each of these. e.g. SQS for queueing and a relational store for others.

kymr commented 6 years ago

System Tasks

To create system tasks follow the steps below:
- Extend com.netflix.conductor.core.execution.tasks.WorkflowSystemTask
- Instantiate the new class as part of the startup (eager singleton)

kymr commented 6 years ago

Check it

I should extend conductor backeds
dynomite to redis cluster or other reliable solution
not sure for replacing ES5
check the code and make sure we understand deeply and predict any issues that may arise during the change