proposals
cadence
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.
proposals
-
Is there an alternative for Airflow for running thousands of dynamic tasks?
Check out temporal.io open source project. It was built at Uber for large scale business-level processes. So any data pipelines are low-rate use cases by definition.
-
KuFlow as a Temporal.io-based Workflow Orchestrator
With KuFlow it is also possible to work with serverless workflows apart from Temporal.io, we explain it in this blog entry, but in summary, almost as a no-code tool, the correct use It would be a rather low-code tool; in just a matter of minutes with our drag-and-drop tool, you can have a workflow that interacts with one or more users of the organization.
-
How to handle background jobs in Rust?
Otherwise you may want to look into Kafka or Fluvio to ensure that task runs at least once. If you're doing something like batch operations as a background task, Temporal is another great option.
-
No-code or Workflow as code? Better both
The runtime is developed using Temporal, which is one of the main tools that we are currently using at KuFlow. Thanks to, all the workflow executions are robust: your application will be durable, reliable, and scalable.
-
Temporal Programming, a new name for an old paradigm
Hmmm I got confused by the name. I thought it's related to https://temporal.io/
-
Possible innovations in Event Sourcing frameworks.
Have you looked at temporal.io open source platform? It uses event sourcing as an implementation detail. But it greatly simplifies the user experience compared to "raw event sourcing."
-
After Airflow. Where next for DE?
Rewrite Airflow on top of temporal.io. This way, you get unlimited scalability and very high reliability out of the box and would be able to innovate on the features that matter for DE.
-
Show HN: Retool Workflows – Cronjobs, but better
Hi all, founder @ Retool here. Over the past year, we’ve been working on Retool Workflows; a fast way for engineers to automate tasks with code. We started building the product because we ourselves (as developers) were looking for something in-between writing cron jobs (which involves a lot of boilerplate) and Zapier (which oftentimes isn’t customizable enough, since it doesn’t _really_ support writing code).
Workflows is a code-first automation tool: you’re _expected_ to write code, but we handle all the boilerplate for you. For example: out-of-the-box integration with 80+ resources (you probably don’t want to be trying to figure out OAuth 2.0 with Salesforce!), monitoring and observability (so you can see the output of every run in the past, and immediately be notified if something goes wrong), and permissions (e.g. some Okta groups can see the outputs of Workflows, but can’t change the code itself).
Right now, the product is cloud-only, but we’re hard at work at an on-prem, self-hosted version (in a Docker image). If you’re interested in that version, feel free to email us at [email protected]. We aim to get it out in the next few weeks. Self-hosted Retool is responsible for a large portion of our usage today, and we’re excited to be supporting Workflows too.
All Retool plans now include 1GB of Workflows throughput, which we think is quite generous (80% of active Workflows users are below 1GB). We don’t bill by run at all, so you’re welcome to run as many workflows as you want.
We use a bunch of interesting technology for Workflows; we are, for example, using Temporal (https://temporal.io/) under the hood. That’s something we’re going to be writing a blog post about later. (We’ve been hard at work on the launch, hah.)
-
How KuFlow supports Temporal as a worfkows engine for our processes?
In such a diverse world, it would be boring to have a single way of doing things. That's why at KuFlow we support different ways to implement the logic of our processes and tasks. And in this post, we will talk about one of them, the orchestration through Temporal, which gives us a powerful way to manage our workflows.
- Library for manage tasks when make a workflow automation.
cadence
- Show HN: Hatchet – Open-source distributed task queue
-
Ask HN: Who is hiring? (December 2023)
Uber | Software Engineers | Hybrid (Denmark) | https://www.uber.com/dk/en/careers/locations/aarhus/
Work with an amazing team responsible for the infrastructure software that makes Uber’s data centers around the world reliable and scalable. If you want to solve the toughest engineering challenges alongside some of the smartest people in the industry, Uber Aarhus is the right place for you.
The team in Aarhus build and operate the stateless and stateful compute platforms used by nearly every other engineer in the company (Up - https://www.uber.com/en-GB/blog/up-portable-microservices-re... and Odin - https://www.uber.com/en-GB/blog/how-uber-optimized-cassandra...) as well as other related infrastructure projects such as Cadence - https://github.com/uber/cadence.
- Cadence – Fault-Tolerant Stateful Code Platform by Uber
-
Best way to schedule events and handle them in the future?
May be this..https://cadenceworkflow.io/
- Mandala: experiment data management as a built-in (Python) language feature
-
are you interested in an end to end queue/pubsub & worker platform
a managed esb orchestration for example is exactly same as step functions and workflow engines like cadence - https://github.com/uber/cadence
-
Why messaging is much better than REST for inter-microservice communications
Having done a reasonable amount of messaging code in my time, I would say the final form of this sort of thing might look more like Cadence[0] than anything like this.
[0] https://github.com/uber/cadence
-
cadence VS javactrl-kafka - a user suggested alternative
2 projects | 2 Feb 2023
- Fault-Tolerant Stateful Code Platform
-
[P] My co-founder and I quit our engineering jobs at AWS to build “Tensor Search”. Here is why.
Emit events from your primary DB (postgres, etc.) to something like kafka or rabbitmq and then catch that in your search engine. There's also some end-to-end solutions like temporal (temporal.io) or cadence (https://cadenceworkflow.io/)
What are some alternatives?
conductor - Conductor is a microservices orchestration engine.
temporal - Temporal service
temporalite-archived - An experimental distribution of Temporal that runs as a single process
Flowable (V6) - A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.
zenml - ZenML 🙏: Build portable, production-ready MLOps pipelines. https://zenml.io.
gocelery - Celery Distributed Task Queue in Go
seldon-core - An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models
Asynq - Simple, reliable, and efficient distributed task queue in Go
kubemq-community - KubeMQ is a Kubernetes native message queue broker
docker-compose - Temporal docker-compose files
nextjs-cron - Cron jobs with Github Actions for Next.js apps on Vercel▲
Faktory - Language-agnostic persistent background job server