contribsys/faktory

Language-agnostic persistent background job server

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 10th, 2026
Created on June 15th, 2017
Open Issues & Pull Requests: 23 (+0)
GitHub issues: Enabled
Number of forks: 239
Total Stargazers: 6,145 (+0)
Total Subscribers: 63 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 544 days
Stale 30+ days: 7
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • fent (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Faktory is a language-agnostic persistent background job server that acts as a centralized repository for distributing work across multiple machines and programming languages.

Faktory solves the problem of coordinating asynchronous work across distributed systems. It stores jobs as JSON objects in queues and allows workers written in any language to fetch and execute them through a standardized API. Jobs are reserved with a timeout, defaulting to thirty minutes; if a job fails or is not acknowledged within that window, it is automatically requeued. Failed jobs trigger a retry workflow with exponential backoff, ensuring resilience without requiring retry logic in client code.

The tool suits teams running polyglot environments where multiple programming languages need to coordinate background work, or organizations scaling from a single machine to many. It provides a Web UI for job management and monitoring, making it accessible to operators who need visibility into queue health and job execution. Faktory is particularly valuable when you need language-agnostic job distribution rather than language-specific solutions tied to a particular framework or ecosystem.

The project maintains active continuous integration and receives ongoing development attention. Documentation is comprehensive and centralized in a wiki alongside installation guides for multiple deployment scenarios including Docker and AWS ECS. Community support is available through both GitHub discussions and a dedicated forum tag, indicating sustained engagement with users.