-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a plan to support microservice orchestration? #74
Comments
@qqeasonchen Maestro is optimized for data platform user cases, which is different from micro-service orchestration. In micro-service orchestration, micro services usually pull tasks from the orchestrator. But Maestro manages the task lifecycle directly and push tasks to the execution engine. Some users use Maestro to achieve it to make the micro service to be an execution engine. For example, let microservice to have REST endpoints to run the business logic and also able to return the job progress. Then maestro workflow will use a RestAPI job to call the microservice endpoint to run the business logic. Next Maestro workflow will poll the job status from the microservice til the job is done. |
can we get any examples on http task workflow, i want to create a workflow with 3 http tasks where my buisiness logic resides. |
Is there a plan to support microservice orchestration like Conductor or only for the data platform? thanks.
The text was updated successfully, but these errors were encountered: