Gearman

Lightweight job server that farms work out to workers from an in-memory queue.

Provider: default
Kind: Queue
Category: Messaging
Official docs: https://gearman.org/documentation/

Properties · 5 set by this component

property	type	values	required	kind default	this component
backoff	enum	none \| fixed \| exponential \| exponential-jitter	no	—	inherited
deadLetterQueue	boolean	—	no	false	▸ false
delivery	enum	at-most-once \| at-least-once \| exactly-once	yes	—	▸ at-most-once
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	inherited
maxAttempts	integer	—	no	—	inherited
ordering	enum	none \| per-key \| global	no	none	▸ none
persistence	boolean	—	no	true	▸ false
replay	boolean	—	no	false	▸ false
retentionDays	integer	—	no	—	inherited
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	inherited

Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Queue without dead-letter queueerror

queue-missing-dlq

A queue that receives asynchronous traffic and has no dead-letter queue either drops poison messages or retries them forever. Neither outcome leaves anything for a human to investigate.

— all of these hold:
— the node's `deadLetterQueue` is false
— the node has at least one asynchronous incoming edge

Retry queue without dead-letter queueerror

retry-queue-without-dlq

A retry queue is where poison messages end up. With no dead-letter queue they are retried forever or dropped in silence, and nobody ever looks at the failed payment.

— all of these hold:
— the node's `role` is "retry"
— the node's `deadLetterQueue` is false

Retry queue without backoffwarning

retry-without-backoff

Retrying a transient failure at full speed turns one slow dependency into a retry storm. A retry queue backs off, preferably exponentially and with jitter.

— all of these hold:
— the node's `role` is "retry"
— any of these hold:
— the node's `backoff` has no value
— the node's `backoff` is "none"

Use it in a design

nodes:
  - { id: "gearman", component: "gearman" }

Other Queue products · 23

Simple Message Queue (formerly MNS)alibaba-mnsalibabacloudqueue ApsaraMQ for RabbitMQalibaba-rabbitmqalibabacloudqueue ApsaraMQ for RocketMQalibaba-rocketmqalibabacloudqueue Amazon MQaws-mqawsqueue Amazon SQSsqsawsqueue Azure Queue Storageazure-queue-storageazurequeue Azure Service Busazure-service-busazurequeue Cloudflare Queuescloudflare-queuescloudflarequeue Apache ActiveMQactivemqqueue IBM MQibm-mqqueue Message queuemessage-queuequeue NSQnsqqueue Apache Qpid Broker-Jqpidqueue Generic queuequeuequeue RabbitMQrabbitmqqueue Redis queueredis-queuequeue Solace PubSub+ Event Brokersolacequeue TIBCO Enterprise Message Servicetibco-emsqueue Google Cloud Tasksgoogle-cloud-tasksgcpqueue IBM Cloud Messages for RabbitMQibm-messages-for-rabbitmqibmqueue IBM MQ on Cloudibm-mq-on-cloudibmqueue OCI Queueoci-queueociqueue OpenStack Zaqaropenstack-zaqaropenstackqueue

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Gearman job server: in-memory queue with no persistence unless a persistent backend is configured,
3# so a server restart drops queued jobs.
4schemaVersion: "1"
5type: "component"
6id: "gearman"
7kind: "queue"
8provider: "default"
9docs: "https://gearman.org/documentation/"
10defaults:
11  delivery: "at-most-once"
12  ordering: "none"
13  deadLetterQueue: false
14  replay: false
15  persistence: false

The same page as markdown, for an agent: /catalogue/components/gearman.md