Component
core/compute/worker
A generic background-worker primitive. Its operational type is `worker` — long-running, stateless compute that pulls from queues or runs background loops with zero inbound application ports — and it adds two optional integer fields, `queue_depth_hint` and `concurrency`, to the shared base schema's documentation knobs. An Aggregate declares this for a component that consumes work rather than accepting inbound application traffic, which is what `server` is for. Declaring no `provides`, it publishes nothing across an edge. On a Kubernetes cluster it is a Deployment. In an AWS account with an ECS cluster and a VPC, terraform/worker-ecs and cloudformation/worker-ecs run it as an Amazon ECS service on Fargate. In a Google Cloud project with a VPC network, terraform/worker-cloud-run runs it as a Cloud Run worker pool; in an Azure subscription with a Container Apps environment, terraform/worker-container-apps as a container app with no ingress. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The image is the Release's own code, so an edge from this component delivers what its `inject:` block dictates: `env` entries become variables everywhere, beside both values' default names, which the component's own `env` entries may replace and, while each is the default, no edge may dictate; `file` entries files on Kubernetes and Container Apps alone; and `arg` or any other mechanism is refused by name, as no realization renders a command line. A `core/secret-value` attachment's value is rendered in the clear on every realization; no realization delivers `core/referenced-secret` or `core/random-password` to it, and the helm realization refuses either by name.
Provenance
- Content digest
- sha256:eaf961fd361445f4512b58fad46e497d53ac752d243406b9395ec8b3c8110bb3
- Published
- 2026-11-10T10:10:20Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:13aedbc915f892c29dda59a0edb42204121785a99b8bcf9817edaeef5420153b
Reference at this version
oci://hub.aggrega.ai/component/core/compute/worker:1.0.0Developer parameters
Values the developer sets in the Aggregate.
Extends BaseComponents#/schemas/BaseComponentParameter
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| queue_depth_hint | integer (min 0) | — | no | — |
| concurrency | integer (min 1) | — | no | — |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| image | string | — | no | Container image running the worker loop. |
| replicas | integer (min 1) | 1 | no | Replica count, the number of tasks on Amazon ECS, of instances in a Cloud Run worker pool and of replicas on Container Apps, up to 300 there. Each replica pulls its own work, so raising it widens throughput rather than sharing one queue position. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads: the Amazon ECS realizations read the cluster, subnets, security groups and roles the service runs under, each under its target's own spelling (subnet_ids on terraform, Subnets on CloudFormation), the Cloud Run realization the project, region, VPC network and service account the worker pool runs in, the Container Apps realization the environment and resource group the app runs in and the identities and registry it pulls with, and the Kubernetes realization reads none of its keys. |
Output contract
Values this component publishes to consumers over the uses topology.
No output values declared.
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
No attachment slots declared.
Self-inject allowlist
env
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
- $refextends schema (values)
BaseComponents#/schemas/BaseComponentParameter
Used by
uses socket «scrape_target»
applies to
applies to
applies to
implements
implements
implements
implements
implements