conductor-oss / conductor-oss/conductor
[FEATURE]: Support interface level orchestration
- Dominant language
- Java
- Stars
- 32.2k
- Forks
- 1k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 41
Description
### Discussed in https://github.com/orgs/conductor-oss/discussions/388
Originally posted by **mytang0** February 12, 2025
Interface-level orchestration refers to arranging the logic of the interface into a workflow (such as HTTP requests), so that each interface request triggers a process instance while meeting the RT requirements of the interface.
In this respect, I share an attempt that stands on the shoulders of the 'Conductor' project. [An orchestration engine, supports microservices and in-app logic (embedded use) orchestration](https://github.com/mytang0/brook)
Contributor guide
Research direction
Read discussion 388 and the linked Brook project first; no repository file, test, or entry point is named in the issue. Define the requested interface-level orchestration scope and RT requirements before implementation, with completion requiring an agreed design and concrete acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100