This has been discussed on https://github.com/orgs/conductor-oss/discussions/108 and directly with Orkes. After the discussion we have come to a conclusion that commercial use of default Orkes queues in conductor is not allowed without a license agreement with Orkes and doesn't meet the overall Apache 2.0 license of Conductor.
Current use of Orkes queues needs licensing for commercial use and isn't Apache 2.0 compliant.
Prior to Orkes queues the default implementation for Netflix dyno queues which is Apache 2.0 license.
Describe Preferred Solution
Revert default queue implementation to dyno queues as it existed prior to Orkes in the the OSS version of Conductor to make it Apache 2.0 licensed across all of conductor.
This has been discussed on https://github.com/orgs/conductor-oss/discussions/108 and directly with Orkes. After the discussion we have come to a conclusion that commercial use of default Orkes queues in conductor is not allowed without a license agreement with Orkes and doesn't meet the overall Apache 2.0 license of Conductor.
The issue is similar to what was brought up earlier with licensing on https://github.com/Netflix/conductor/issues/2091
Describe the Feature Request
Current use of Orkes queues needs licensing for commercial use and isn't Apache 2.0 compliant. Prior to Orkes queues the default implementation for Netflix dyno queues which is Apache 2.0 license.
Describe Preferred Solution
Revert default queue implementation to dyno queues as it existed prior to Orkes in the the OSS version of Conductor to make it Apache 2.0 licensed across all of conductor.
Describe Alternatives
Update license of Orkes queues to Apache 2.0