PowerJob
Redisson
PowerJob | Redisson | |
---|---|---|
9 | 3 | |
6,489 | 22,769 | |
1.1% | 0.9% | |
8.3 | 9.9 | |
20 days ago | 1 day 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.
PowerJob
- Distributed job-scheduling framework of the next generation - PowerJob
-
JobRunr VS PowerJob - a user suggested alternative
2 projects | 21 Dec 2021
-
PowerJob V3.4.3 has been released. Check to see the work. Suggestions are welcomed.
Oh yes! You can see the registered users in Known users. They are companies in China as we didn't promote to foreign friends. Cisco, Jd.com, OPPO are all big companies there in China.
-
My experience of hunting for job-scheduling framework
And frankly the readme on https://github.com/PowerJob/PowerJob should be rewritten. Texts in the line of "PowerJob is the best thing since sliced bread" has no place in open source. Explain what it does well, what it doesn't do well, where it can be used, where it should not be used, and how it works.
- PowerJob - Distributed job-scheduling framework of the next generation for Java Applications.
- Next generation of job-scheduling framework - PowerJob
- Distributed job-scheduling framework of the next generation - PowerJob!
Redisson
-
Kotlin Spring WebFlux, R2DBC and Redisson microservice in k8s 👋✨💫
Source code you can find in the GitHub repository. he main idea of this project is the implementation of microservice using Kotlin, Spring WebFlux, PostgresSQL, and Redis with metrics and monitoring and deploying it to k8s. For interacting with PostgresSQL we will use reactive Spring Data R2DBC and for Redis caching using Redisson.
-
Am I overlooking any potential issues that could arise from my implementation?
I came up empty handed in search of an alternative to Quartz for scheduling Crons in a clustered/distributed environment. Redisson has a scheduler, but it came with its own issues: - https://github.com/redisson/redisson/issues/4020 - https://github.com/redisson/redisson/issues/3991 - https://github.com/redisson/redisson/issues/4321
-
Implement Hibernate 2nd level Cache with Redis, Spring Boot, and Spring Data JPA
4. We use the open-source library Redisson to connect to Redis instance and use Redis as Hibernate 2nd level cache. Please see their Github repo for more information.
What are some alternatives?
db-scheduler - Persistent cluster-friendly scheduler for Java
Jedis - Redis Java client
JobRunr - An extremely easy way to perform background processing in Java. Backed by persistent storage. Open and free for commercial use.
Hazelcast - Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.
kestra - Infinitely scalable, event-driven, language-agnostic orchestration and scheduling platform to manage millions of workflows declaratively in code.
Chronicle Map - Replicate your Key Value Store across your network, with consistency, persistance and performance.
openjob - Distributed high performance task scheduling framework
Ehcache - Ehcache 3.x line
Sundial - A Light-weight Job Scheduling Framework
MapDB - MapDB provides concurrent Maps, Sets and Queues backed by disk storage or off-heap-memory. It is a fast and easy to use embedded Java database engine.
Wisp - A simple Java Scheduler library with a minimal footprint and a straightforward API
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM