Our great sponsors
Quartz | proposals | |
---|---|---|
18 | 60 | |
6,065 | 63 | |
1.1% | - | |
3.6 | 4.0 | |
18 days ago | 16 days ago | |
Java | ||
Apache License 2.0 | MIT License |
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.
Quartz
-
Open source Job Scheduler Library in java for high throughput
In java we have found Quartz( Quartz) , Job Runr(Jobrunr) and db-scheduler(db-scheduler) and need to evaluate these for our use case.
-
what technologies are people using for job scheduling in/with k8s?
Im mit sit what you mean by "not supported", you sure can run MongoDB on Kubernetes. Maybe I'm way off, are you saying that you can't use Quartz (this one: http://www.quartz-scheduler.org/ ?) because it doesn't natively allow you to load from MongoDB and.therefor you can't use it?
-
FF4J – Feature Flags for Java
Uh this class is even worse, SDF is not a thread safe date formatter, so it never should be `final static`. `releaseDate` and `new Date()` will be ignorant of summer/winter time changes. For such scheduling one should use Quartz https://www.quartz-scheduler.org/
- Delay processing request without blocking request
-
scheduling system for backend
Have a look at http://www.quartz-scheduler.org/ If you're using Java
- I am looking for a replacement for Quartz job scheduler for our Java enterprise app. Last version of Quartz came out over 4 years ago and the project looks like it's been abandon since them. Any help is appreciated and thanks in advance.
- Suggestions for a distributed job queue lib?
-
Lightweight background job runner framework?
Long time I used http://www.quartz-scheduler.org which worked nicely, I wonder why Scala does not seem to have something standard for this.
-
Does Spring offer Event trigger?
Quartz Scheduler
-
Cron jobs in cluster
We have a separate service for running cron jobs. It uses Quartz (http://www.quartz-scheduler.org/) and it has a REST API that we use to submit new jobs. It's easy to set up and all you need is a database. You definitely need a database in order to synchronize across different containers.
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.
What are some alternatives?
JobRunr - An extremely easy way to perform background processing in Java. Backed by persistent storage. Open and free for commercial use.
conductor - Conductor is a microservices orchestration engine.
Google Web Toolkit - GWT Open Source Project
temporalite-archived - An experimental distribution of Temporal that runs as a single process
flask-apscheduler - Adds APScheduler support to Flask
zenml - ZenML 🙏: Build portable, production-ready MLOps pipelines. https://zenml.io.
Apache Ant - Apache Ant is a Java-based build tool.
seldon-core - An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models
cglib - cglib - Byte Code Generation Library is high level API to generate and transform Java byte code. It is used by AOP, testing, data access frameworks to generate dynamic proxy objects and intercept field access.
kubemq-community - KubeMQ is a Kubernetes native message queue broker
Dkron - Dkron - Distributed, fault tolerant job scheduling system https://dkron.io
nextjs-cron - Cron jobs with Github Actions for Next.js apps on Vercel▲