Creating a Web Endpoint
Deploying and invoking web endpoints on Beam
Beam allows you to deploy web endpoints that can be invoked via HTTP requests. These endpoints can be used to run arbitrary code. For instance, you could perform inference using one of our GPUs, or just run a simple function that multiplies two numbers.
Endpoints vs. Task Queues
Endpoints are RESTful APIs, designed for synchronous tasks that can complete in ~30s or less. For longer running tasks, you’ll want to use an asynchronous task_queue
instead.
Launch a Preview Environment
beam serve
monitors changes in your local file system, live-reloads the remote environment as you work, and forwards remote container logs to your local shell.
Serve is great for prototyping. You can develop in a containerized cloud environment in real-time, with adjustable CPU, memory, GPU resources.
It’s also great for testing an app before deploying it. Served functions are orchestrated identically to deployments, which means you can test your Beam workflow end-to-end before deploying.
To start an ephemeral serve
session, you’ll use the serve
command:
By default, Beam will sync all the files in your working directory to the
remote container. This allows you to use the files you have locally while
developing. If you want to prevent some files from getting uploaded, you can
create a .beamignore
.
Deploying the Endpoint
To deploy the endpoint, enter your shell and run this command from the working directory:
After running this command, you’ll see some logs in the console that show the progress of your deployment.
Calling the Endpoint
After deploying the API, you’ll be able to copy a cURL request to hit the API. Open another terminal window to invoke the API:
Example Request
Example Response
Was this page helpful?