Gearman vs IronWorker

Gearman is a free, self-hosted application framework for distributing work across machines or processes. A client submits jobs, a job server routes them, and a worker performs them, allowing parallel processing and load balancing. Jobs can run asynchronously in the background or receive priorities. Clients and workers may use different language interfaces when they understand the workload; listed interfaces include C, C#/.NET, Go, Java, Node.js, PHP, Perl, Python, Ruby, Rust, and Lisp. Messages can reach 4 GB, with chunking for larger messages. Clients and workers can connect to multiple job servers and fail over when one dies. The C job server supports persistent queues. MySQL and PostgreSQL functions expose client calls to queries, triggers, and stored procedures, while the pure Perl API supports SSL. Gearman runs on Linux and Windows, offers API access, and is licensed under BSD. GearmanSharp is incomplete.

IronWorker is a container-based platform for running custom code as queued, asynchronous background tasks. It supports parallel processing, and jobs can run once, a set number of times or on a recurring schedule. Workers run in Docker containers and support Ruby, Python, PHP, Java,.NET, Node.js and Go. Tasks can be triggered by HTTP POST webhooks, other workers or IronMQ queues; the Iron.io dashboard displays task status and performance. The platform describes SSL connections, isolated Docker sandboxes and OAuth2 for task execution. Deployment choices include shared, dedicated, hybrid and on-premise environments. Listed uses include image and video processing, push notifications, ETL, email delivery and cron replacement. Basic costs nothing and includes five hours per month, one concurrency, 512 MB RAM and a 30-minute runtime. Standard costs $169 a month and includes unlimited hours with ten concurrency. Premium costs $699 a month. A 14-day trial is available only for non-dedicated clusters.