conductor
kestra
Our great sponsors
conductor | kestra | |
---|---|---|
39 | 32 | |
12,999 | 6,340 | |
- | 14.7% | |
8.4 | 9.9 | |
5 months ago | 2 days ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
conductor
- Netflix Conductor OSS discontinued support
-
Orkes Monthly Highlights - October 2023
We celebrated a remarkable milestone in September when the Netflix Conductor GitHub repository reached 10k stars. It was a momentous achievement for our DevRel team. Just a month later, we're thrilled to announce that we've surpassed 12k stars! ⭐🎉
-
4 Microservice Patterns Crucial in Microservices Architecture
Also, don’t forget to give us a ⭐ on our Netflix Conductor repo.
-
The Workflow Pattern
One of my favorite workflow engines that has a really simple way to do things was not listed here, so I'll call it out - Netflix Conductor (https://github.com/Netflix/conductor).
Its capabilities comes to light when you model really complex workflows and one real value is how its all very visual not just during modeling but when running it. The history remains visible and you can even see how the whole flow evolved.
-
Orkes Monthly Highlights - September 2023
Yet another significant milestone on our journey: we've proudly reached the 10,000-star mark on our Netflix Conductor GitHub repository! 🌟
-
question about microservice to microservice internal only communication
Give something like https://github.com/Netflix/conductor a try to solve this -- makes it very easy to do what you are trying to achieve.
- Framework used by Netflix to orchestrate microservices
-
Background Task Management on Celery and EC2
Checkout Conductor https://github.com/Netflix/conductor which is far more scalable and easy on the resources with its own Celery like queues. Fully supports writing task workers in python:
- Implementing Saga Pattern in Go Microservices
- GitHub - Netflix/conductor: Microservices orchestration engine.
kestra
-
A High-Performance, Java-Based Orchestration Platform
Kestra's communication is asynchronous and based on a queuing mechanism. It leverages the Micronaut framework and offers two runners: one that uses a database (JDBC) for both the message queue and resource storage, and another that uses Kafka as the message queue and Elasticsearch as the resource storage. The platform is fully extensible and plugin-based, providing a rich set of plugins for various workflow tasks, triggers, and data storage options. For those interested, the GitHub repository is available here: https://github.com/kestra-io/kestra
- Kestra is an open-source data orchestration platform for complex workflows
- YAML-based data orchestrator
- Kestra
-
Introduction to Kestra, the open source data orchestration and scheduling platform
For everyone wondering https://github.com/kestra-io/kestra/discussions/468
-
Snowflake data pipeline with Kestra
If you need any guidance with your Snowflake deployment, our experts at Kestra would love to hear from you. Let us know if you would like us to add more plugins to the list. Or start building your custom Kestra plugin today and send it our way. We always welcome contributions!
-
Airflow's Problem
But I totally agree that a large static dag is not appropriate in the actual data world with data mesh and domain responsibility.
[0] https://github.com/kestra-io/kestra
-
Ask HN: Open-source with Kafka as dependencies, is this a instant turn off?
- We have plans to add another option that will replace both dependencies with jdbc (https://github.com/kestra-io/kestra/pull/368), is theses dependencies more comfortable for you?
-
ELT vs ETL: Why not both?
With Kestra's innate flexibility, and many integrations, you are not locked into the choice of one ingestion method or the other. Complex workflows can be developed, whether in parallel or sequentially, to deliver both ELT and ETL processes. Simple descriptive yaml is used to connect plugins, and to create flows. Because workflows created in Kestra are represented visually, and issues can be seen in relation to individual tasks, there is no need to fear complexity. Trouble can be traced to its source in an instant, allowing you to try new things and come up with a new solution without fear. Give it a try, and let us know what you come up with!
-
Debezium Change Data Capture without Kafka Connect
Kestra is an orchestration and scheduling platform that is designed to simplify the building, running, scheduling, and monitoring of complex data pipelines. Data pipelines can be built in real-time, no matter how complex the workflow, and can connect to multiple resources as needed (including Debezium).
What are some alternatives?
camunda-demo - 🗞️ Repo for this series: https://dev.to/tgotwig/getting-started-with-camunda-spring-boot-2gbi
zeebe - Distributed Workflow Engine for Microservices Orchestration
Activiti - Activiti is a light-weight workflow and Business Process Management (BPM) Platform targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It's open-source and distributed under the Apache license. Activiti runs in any Java application, on a server, on a cluster or in the cloud. It integrates perfectly with Spring, it is extremely lightweight and based on simple concepts.
kogito-runtimes - This repository is a fork of apache/incubator-kie-kogito-runtimes. Please use upstream repository for development.
proposals - Temporal proposals
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
akhq - Kafka GUI for Apache Kafka to manage topics, topics data, consumers group, schema registry, connect and more...
Springy-Store-Microservices - Springy Store is a conceptual simple μServices-based project using the latest cutting-edge technologies, to demonstrate how the Store services are created to be a cloud-native and 12-factor app agnostic. Those μServices are developed based on Spring Boot & Cloud framework that implements cloud-native intuitive, design patterns, and best practices.
flyte - Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
blockchain-springboot - Run a local blockchain node on your local machine and run different agents on the network, With 3 different replacement functions.
PowerJob - Enterprise job scheduling middleware with distributed computing ability.