Zeema
New design
Catalogue / worker

DigitalOcean Functions

digitaloceanWorkerdigitalocean-functions

On-demand serverless functions invoked over HTTP, on a schedule or asynchronously.

Provider
digitalocean
Kind
Worker
Category
Compute
Official docs
https://docs.digitalocean.com/products/functions/
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
acceleratorenumnone | gpu | asicnononeinherited
concurrencyinteger—no—▸ 120
fanoutStrategy · advancedenumnone | push | pull | hybridnononeinherited
fanoutThreshold · advancedinteger—no—inherited
idempotentboolean—nofalseinherited
instancesinteger—no—inherited
invocationsPerMinute · component propertyinteger—no600inherited
managedboolean—nofalse▸ true
maxTimeoutMinutes · component propertyinteger—no15inherited
memoryMb · component propertyinteger—no256inherited
rateControl · advancedenumnone | fixed | aimdnononeinherited
runtime · component propertyenumgo | node | php | pythonno—inherited
schedulestring—no—inherited
triggerenumqueue | stream | schedule | batch | manualyes—▸ manual
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.

Push fan-out without a celebrity thresholdwarning
push-fanout-without-celebrity-path

Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.

  • — all of these hold:
  • — the node's `fanoutStrategy` is "push"
  • — the node's `fanoutThreshold` has no value
  • — the design contains a node of kind graph-database
Shared worker pool across queueswarning
shared-worker-pool-across-queues

One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.

  • — all of these hold:
  • — the node has more than 1 incoming edge from a queue
  • — the design requirement `isolation.perQueue` is true
Stateful node without zone redundancyerror
stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

  • — all of these hold:
  • — the node's `stateless` is false
  • — the node sits inside exactly 1 availability-zone group
  • — this does not hold:
  • — the node sits inside at least one cell group
Use it in a design
nodes:
  - { id: "functions", component: "digitalocean-functions" }
Other Worker products · 82
SchedulerXalibaba-schedulerxalibabacloudworkerAmazon AppFlowaws-appflowawsworkerAWS B2B Data Interchangeaws-b2b-data-interchangeawsworkerAWS Batchaws-batchawsworkerAWS Glue DataBrewaws-databrewawsworkerAWS DataSyncaws-datasyncawsworkerAWS Deadline Cloudaws-deadline-cloudawsworkerAWS Entity Resolutionaws-entity-resolutionawsworkerAmazon EventBridge Scheduleraws-eventbridge-schedulerawsworkerAWS Fault Injection Serviceaws-fisawsworkerAWS Glue crawleraws-glue-crawlerawsworkerAWS Glue for Ray jobaws-glue-ray-jobawsworkerAWS Application Migration Serviceaws-mgnawsworkerAmazon MSK Connectaws-msk-connectawsworkerAmazon SageMaker AI Training Jobaws-sagemaker-training-jobawsworkerAWS Systems Manageraws-systems-managerawsworkerAWS Thinkbox Deadline 10aws-thinkbox-deadlineawsworkerAWS Glue jobglue-jobawsworkerAzure Automationazure-automationazureworkerAzure Batchazure-batchazureworkerAzure Chaos Studioazure-chaos-studioazureworkerAzure Data Factoryazure-data-factoryazureworkerAzure Data Shareazure-data-shareazureworkerAzure Database Migration Serviceazure-database-migration-serviceazureworkerMicrosoft Entra Connect Syncazure-entra-connect-syncazureworkerMicrosoft Graph Data Connectazure-graph-data-connectazureworkerAzure Storage Moverazure-storage-moverazureworkerAzure Update Managerazure-update-managerazureworkerBrowser Runcloudflare-browser-runcloudflareworkerCloudflare Snippetscloudflare-snippetscloudflareworkerCloudflare Zarazcloudflare-zarazcloudflareworkerAirbyteairbyteworkerAirflow DAGairflow-dagworkerChaos Meshchaos-meshworkerChunkrchunkrworkerContainer workercontainer-workerworkerCron jobcron-jobworkerDaytonadaytonaworkerE2Be2bworkerEmbulkembulkworker
and 42 more → Worker page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# DigitalOcean Functions: "blocks of code that run on demand without the need to manage any
# infrastructure", deployed into a namespace and invoked over HTTP, on a schedule or
# asynchronously ("Functions"). "Functions Limits": memory defaults to 256 MB within a
# 128 MB - 1 GB range, the maximum timeout is 15 minutes including initialization, and a
# namespace runs up to 120 concurrent functions at up to 600 invocations per minute.
schemaVersion: "1"
type: "component"
id: "digitalocean-functions"
kind: "worker"
provider: "digitalocean"
docs: "https://docs.digitalocean.com/products/functions/"
defaults:
  managed: true
  trigger: "manual"
  concurrency: 120
properties:
  runtime:
    type: "enum"
    values: ["go", "node", "php", "python"]
  memoryMb:
    type: "integer"
    default: 256
  maxTimeoutMinutes:
    type: "integer"
    default: 15
  invocationsPerMinute:
    type: "integer"
    default: 600

The same page as markdown, for an agent: /catalogue/components/digitalocean-functions.md