3 个仓库
Durable storage of queue state and job metadata to prevent data loss during crashes.
Distinct from Task Output Persistence: Distinct from Task Output Persistence: focuses on persisting the queue state for recovery, not logs of completed tasks.
Explore 3 awesome GitHub repositories matching data & databases · Job Queue Persistence. Refine with filters or upvote what's useful.
Beanstalkd is a distributed work queue server designed for asynchronous job processing. It functions as a standalone server that distributes background tasks between producers and consumers to improve application responsiveness and throughput. The system organizes tasks using numeric priority levels to ensure critical work is processed first. It manages the job lifecycle through discrete states and uses a simple line-based text protocol over TCP for communication. To ensure reliability, the server persists job data to a sequential disk log, allowing the queue state to be recovered after a sy
Persists job data to disk to ensure work is not lost during server restarts or system crashes.
Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to support real-time analytics and event-driven applications. It functions as a partitioned, distributed key-value store that replicates data across cluster nodes to provide low-latency access and high availability. The platform also serves as a distributed SQL query engine, allowing users to execute standard SQL statements against both in-memory datasets and external data sources. What distinguishes Hazelcast is its use of a distributed consensus subsystem to maintain strongly consis
Integrates a queue with an external datastore to archive items and prevent memory exhaustion by offloading data.
Good Job is a background job processor for Ruby on Rails that utilizes a PostgreSQL database as its primary storage engine. By leveraging relational database transactions, it ensures persistent and reliable task execution, integrating directly with the Active Job framework to handle asynchronous operations and recurring job scheduling within existing application environments. The system distinguishes itself through an in-process execution model that allows background workers to run within the same process as the web server, simplifying deployment by removing the need for separate worker servi
Uses relational database tables as the primary storage engine to ensure transactional integrity and persistence for all queued background tasks.