Job queue system to run job with Docker
Barbeque is used on production at Cookpad.
Barbeque is a job queue system that consists of:
- Web console to manage jobs
- Web API to queue a job
- Worker to execute a job
A job for Barbeque is a command you configured on web console. A message serialized by JSON and a job name are given to the command when performed. In Barbeque worker, they are done on Docker container.
- You can achieve job-level auto scaling using tools like Amazon ECS EC2 Auto Scaling group
- For Amazon ECS, Barbeque has Hako executor
- You don't have to manage infrastructure for each application like Resque or Sidekiq
For details, see Scalable Job Queue System Built with Docker // Speaker Deck.
Install barbeque.gem to an empty Rails app and mount Barbeque::Engine.
And deploy it as you like.
You also need to prepare MySQL, Amazon SQS and Amazon S3.
Barbeque's enqueue API tries to be independent of MySQL by design.
Although that design policy, verifying the enqueued job is useful in some environment (such as sandboxed environment).
Passing BARBEQUE_VERIFY_ENQUEUED_JOBS=1 to the Web API server enables the feature that verifies the enqueued job by accessing MySQL.
$ rake barbeque:worker BARBEQUE_QUEUE=defaultThe rake task launches four worker processes.
- Two runners
- receives message from SQS queue, starts job execution and stores its identifier to the database
- One execution poller
- gets execution status and reflect it to the database
- One retry poller
- gets retried execution status and reflect it to the database
Web API documentation is available at doc/toc.md.
barbeque_client.gem has API client and ActiveJob integration.
Barbeque executor can be customized in config/barbeque.yml. Executor is responsible for starting executions and getting status of executions.
Barbeque has currently two executors.
Barbeque::Executor::Docker starts execution by docker run --detach and gets status by docker inspect.
Barbeque::Executor::Hako starts execution by hako oneshot --no-wait and gets status from S3 task notification.
You must configure CloudWatch Events for putting S3 task notification. See Hako's documentation for detail. https://github.com/eagletmt/hako/blob/master/docs/ecs-task-notification.md
The gem is available as open source under the terms of the MIT License.