Services
Request-driven application units in the Vercel deployment model that typically respond to calls as HTTP services, complementing the long-running process form of Daemons. Services are invoked on demand and scale with incoming requests, while daemons handle persistent background work. Together they allow a single deployment to combine synchronous endpoints with asynchronous processing, with service bindings providing communication between the two forms.
Timeline (last 90 days)
In Vercel's deployment model, Services are request-driven application units that typically respond to calls as HTTP services; Daemons are resident processes whose lifecycle is bound to the deployment, suited to background logic such as workers, queue consumers and scheduled tasks.
Before service bindings, communication between a Daemon and a Service relied on externally exposed HTTP addresses, requiring either making the service public or building a custom internal access channel.
Service bindings are one-way: Services can bind to services outside Daemons, but Services cannot bind to Daemons.
All Facts (3)
In Vercel's deployment model, Services are request-driven application units that typically respond to calls as HTTP services; Daemons are resident processes whose lifecycle is bound to the deployment, suited to background logic such as workers, queue consumers and scheduled tasks.
50%UnverifiedBefore service bindings, communication between a Daemon and a Service relied on externally exposed HTTP addresses, requiring either making the service public or building a custom internal access channel.
50%UnverifiedService bindings are one-way: Services can bind to services outside Daemons, but Services cannot bind to Daemons.
50%