Skip to main content

Serverless

Oyster Serverless allows users to execute functions without having to go through the process of renting and managing an Instance themselves. Users only pay for the time it takes to execute the function. The Serverless protocol requires a set of Instances to always be on standby, ensuring that Requests are served on-demand. These Instances function as shared resources, effectively being 'rented' by multiple users simultaneously.

At the moment, following constraints are imposed on serverless functions:

  • 5% average CPU utilization
  • 100mb RAM
  • 5 minutes max run time
  • workerd sandbox

Requests to execute serverless functions can be submitted via smart contracts or through Web2 APIs. Additionally, the protocol enables users to subscribe serverless requests via smart contracts by scheduling them at regular intervals. The guarantees provided vary depending on the execution mode, and as such, each scenario is addressed by a distinct protocol tailored to its specific requirements.

Learn more about protocol specification and design for Smart Contract and Web2 requests.

Get started with using Oyster Serverless and browse relevant tutorials:

If the constraints of the Serverless protocol don't meet your needs, it may be more suitable to lease a dedicated instance.