Usage Example

Open Google Cloud Console and create a new project (or reuse an existing one).

Google Cloud Project Creation

Make sure to enable Billing to be able to use Cloud Functions, Storage and Datastore.

Enable Cloud Functions Enable Storage

Datastore will be used by the example component to persist data. Make sure to enable it.

Enable Datastore

Finally, requires that the Google Cloud Functions API is enabled as well.

Enable Datastore

Google Cloud is now setup to start using Serverless Web Components. We will use a UpVote Button Component as an example.

At first, download the component and load it in your website. Loading it at the end, just before the </body> tag, is fine.

<script src="/upvote-button.js"></script>

With the script loaded, we now have a new HTML tag: <upvote-button>. The usage of this component requires to set an endpoint attribute according to the Google Cloud project set up above. The endpoint should be constructed like https://{REGION}-{PROJECT_ID} where {REGION} should be replace by the Google Cloud region (probably us-central1 when using Google Cloud Functions) and {PROJECT_ID} should be replaced by your Google Cloud’s project id. This is currently the only kind of supported endpoint. The goal is to add support for other FaaS providers in the future.

With the attribute set, the component’s tag might look like:

<upvote-button endpoint=""></upvote-button>

Since the component’s functions aren’t deployed, yet, you will see a deploy button at first.

Deploy Button

Clicking the deploy button will redirect to the deployment process which prompts for an authorization of the deployment.

Deployment Authorization

Authorizing the deployment requires corresponding access to your Google Cloud account.

Choose an account

The required OAuth scopes are (required for creating Google Cloud Functions) and (required to Upload the source of the Cloud function).

OAuth authorization

Once access according to those scopes has been granted, the deployment is executed and eventually redirected back to your website. After a successful deployment, the deploy button is replaced by the actual component, as shown below.

The deployed component