Skip to content

codaxy/conductor-community

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Conductor OSS community modules

This repository hosts all the community contributed modules and extensions for Conductor OSS

⭐ Conductor OSS

Show support for the Conductor OSS. Please help spread the awareness by starring this repo.

GitHub stars

What is this repository?

Conductor OSS is an extensible platform that allows users to bring in their own persistence, queues, integrations eventing systems such as SQS, NATS, AMQP etc.

For the list of artifacts published please see the table below:

Parent Folder Description
event-queue Support for external eventing systems like AMQP and NATS
external-payload-storage Storage for large workflow payloads
index Indexing for searching workflows
metrics Support for various metrics integrations including Datadog and Prometheus
persistence Persistence for metadata, execution and queue implementation
task Various system tasks - Kafka Publish
lock Workflow execution lock implementation
workflow-event-listener Workflow Status Listener and Binary compatibility with previously published conductor-contribs

FAQ

Why separate repository?

The number of contributions, especially newer implementations of the core contracts in Conductor has increased over the past few years. There is interest in the community to contribute more implementations. To streamline the support and release of the existing community-contributed implementations and future ones, we are creating a new repository dedicated to hosting just contributions. Conductor users who wish to use a contributed module will have a dedicated place to ask questions directly to fellow members of the community.

Having a separate repository will allow us to scale the contributions and also ensure we are able to review and merge PRs in a timely fashion.

How often builds are published?

Similar to core Conductor the builds are published often with each major release. Release numbers are kept in sync with main Conductor releases, which removes the need for a version compatibility matrix.

How do I get help?

Please join the Slack community for help.

How do I add new modules here?

  1. Start with a proposal by posting on the discussion
  2. Send a PR

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Java 96.8%
  • Groovy 3.0%
  • Other 0.2%