Skip to content

Functions

View as Markdown

Functions, also called Function as a Service (FaaS), is E2E’s serverless platform. You write a function, E2E builds and runs it, and you call it over its own public HTTPS URL. You manage no servers. Functions is available in Delhi.

Functions suits jobs that start from an HTTP request and answer quickly. See What you can build for the full set of use cases and the runtimes that suit each one.

  • HTTP APIs and webhooks: a function is one endpoint that handles a request and returns a response. It works well as an API route or a webhook receiver.
  • Your own container: if a runtime template does not fit, deploy your own Docker image as a custom container.

A function runs when an HTTP request calls it. To run code on a schedule, see What you can build.

Each function gets its own public HTTPS URL. A function scales automatically with incoming traffic. More instances start under load, and fewer run when demand drops.

Functions can connect to other cloud services, such as databases, object storage, messaging, and APIs, through the account’s dedicated outbound IP. An external system can allow that one address in its firewall. See Activate Functions.

Functions run on CPU hardware. Choose CPU Functions to write a function in Python, Node.js, Go, C#, or PHP, or Custom Container Image to bring your own Docker image. See Runtimes and hardware. To serve a model on a GPU, use TIR.

To run your first function, follow Get started with Functions. If a function will not deploy or answer, see Troubleshooting Functions. For short answers, see the Functions FAQ, and for how the bill is worked out, Billing.