fix(google): remove support for google cloud functions

Author: acchou

.circleci/config.yml

@@ -109,18 +109,12 @@ workflows:
                   nodeVersion: "node16"
                   executor: node16
                   target: "test-aws"
-            # - build_and_test:
-            #       name: "google-node16"
-            #       nodeVersion: "node16"
-            #       executor: node16
-            #       target: "test-google"
             - examples:
                   nodeVersion: "node16"
                   executor: node16
             - release:
                   requires:
                       - aws-node16
-                      # - google-node16
                       - examples
                   filters:
                       branches:
@@ -142,13 +136,6 @@ workflows:
                   target: "test-aws"
                   requires:
                       - cleanup
-            # - build_and_test:
-            #       name: "google-node16"
-            #       nodeVersion: "node16"
-            #       executor: node16
-            #       target: "test-google"
-            #       requires:
-            #           - cleanup
             - examples:
                   nodeVersion: "node16"
                   executor: node16

README.md

@@ -2,7 +2,7 @@
 
 [![License](https://img.shields.io/badge/License-Apache%202.0-green.svg)](https://opensource.org/licenses/Apache-2.0) [![CircleCI](https://circleci.com/gh/faastjs/faast.js.svg?style=shield&circle-token=c97f196a78c7173d6ca4e5fc9f09c2cba4ab0647)](https://circleci.com/gh/faastjs/faast.js) [![codecov](https://codecov.io/gh/faastjs/faast.js/branch/master/graph/badge.svg?token=Ml90RLLbEh)](https://codecov.io/gh/faastjs/faast.js) [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release) [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Ffaastjs%2Ffaast.js.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Ffaastjs%2Ffaast.js?ref=badge_shield)
 
-Faast.js makes regular functions callable as serverless functions on AWS Lambda and Google Cloud. It handles the details of uploading your code, creating cloud infrastructure, and cleaning up. Scale up your functions to a thousand cores in seconds :rocket:
+Faast.js makes regular functions callable as serverless functions on AWS Lambda. It handles the details of uploading your code, creating cloud infrastructure, and cleaning up. Scale up your functions to a thousand cores in seconds :rocket:
 
 Faast.js is a pure library with no service dependencies, operational overhead, or unnecessary complexity.
 
@@ -71,7 +71,7 @@ $0.00420858
 -   **Cost-effective.** Understand and optimize your workload costs in real time. Pay only for compute time actually used.
 -   **Ephemeral.** No clusters or services to manage. Faast.js creates the infrastructure it uses on the fly and cleans up when it's done.
 -   **Productive.** First class support for TypeScript and JavaScript. Type safety, documentation, and extensive testing are part of our DNA.
--   **Multi-cloud:** Built-in support for AWS Lambda and Google Cloud Functions, as well as local processing mode when you don't have network access. Switch with one line of code.
+-   **Local.** Built-in support for AWS Lambda and local processing mode when you don't have network access. Switch with one line of code.
 
 ## Ready to learn more?
 

build/google-save-key.js

@@ -20,8 +20,6 @@ Using the local provider allows you to test faast.js on your local machine. Ther
 
 AWS is recommended for optimal faast.js performance. See [AWS setup instructions](./04-aws.md#setup).
 
-Google Cloud is also supported. See [Google Cloud setup instructions](./05-google-cloud.md#setup).
-
 ## Usage
 
 Cloud functions can be written as ordinary TypeScript or JavaScript modules:
@@ -109,7 +107,6 @@ Try out different providers:
 
 ```typescript
 await faast("aws", funcs);
-await faast("google", funcs);
 await faast("local", funcs);
 ```
 
@@ -147,15 +144,15 @@ await faast("aws", funcs, {
 });
 ```
 
-Read more about [package dependencies on AWS](./04-aws.md#package-dependencies) and [package dependencies on Google Cloud](./05-google-cloud.md#package-dependencies).
+Read more about [package dependencies on AWS](./04-aws.md#package-dependencies).
 
-Check out even more options in [CommonOptions](./api/faastjs.commonoptions.md) and cloud-specific options in [AwsOptions](./api/faastjs.awsoptions.md), [GoogleOptions](./api/faastjs.googleoptions.md), and [LocalOptions](./api/faastjs.localoptions.md).
+Check out even more options in [CommonOptions](./api/faastjs.commonoptions.md) and cloud-specific options in [AwsOptions](./api/faastjs.awsoptions.md) and [LocalOptions](./api/faastjs.localoptions.md).
 
 ## Terminology
 
-**Provider**: A Functions as a Service (FaaS) provider, such as AWS Lambda or Google Cloud Functions. Faast.js also has a "local" provider which uses child processes to simulate a FaaS service without cloud usage.
+**Provider**: A Functions as a Service (FaaS) provider, such as AWS Lambda. Faast.js also has a "local" provider which uses child processes to simulate a FaaS service without cloud usage.
 
-**faast.js module**, also known as **faast module**: A wrapper around an ordinary JavaScript/TypeScript module that transforms exported ordinary functions into cloud functions. A faast.js module corresponds to a single AWS Lambda or Google Cloud Function that multiplexes requests to all of the functions exported by the module.
+**faast.js module**, also known as **faast module**: A wrapper around an ordinary JavaScript/TypeScript module that transforms exported ordinary functions into cloud functions. A faast.js module corresponds to a single AWS Lambda that multiplexes requests to all of the functions exported by the module.
 
 **Remote function**: A function within a faast.js module instantiated on a provider.
 
@@ -232,10 +229,6 @@ Usage:
 $ npx faastjs cleanup aws
 ```
 
-```shell
-$ npx faastjs cleanup google
-```
-
 Example output:
 
 ```text
@@ -253,8 +246,6 @@ IAM roles
 Lambda layers
 Persistent cache: /Users/achou/.faastjs/aws/pricing
   cache entries: 12
-Persistent cache: /Users/achou/.faastjs/google/pricing
-  cache entries: 5
 Persistent cache: /Users/achou/.faastjs/aws/gc
   cache entries: 1
 Cloudwatch log groups

docs/01-introduction.md

@@ -14,7 +14,7 @@ There's a natural way to use faast.js to maximize developer productivity:
 
 3. Use the `"local"` provider to test your function as a faast.js module. In this mode your invocations execute in local processes. Debug any issues using standard debugging tools you know and love. Make sure your functions are idempotent by invoking them multiple times concurrently with the same arguments.
 
-4. Switch from `"local"` to `"aws"` or `"google"` but limit [concurrency](./api/faastjs.commonoptions.concurrency.md) to a low amount, between 1-10. Use [logUrl](./api/faastjs.faastmodule.logurl.md) to review cloud logs of your code executing. The [DEBUG](#debug-environment-variable) environment variable can be useful to see verbose output as well.
+4. Switch from `"local"` to `"aws"` but limit [concurrency](./api/faastjs.commonoptions.concurrency.md) to a low amount, between 1-10. Use [logUrl](./api/faastjs.faastmodule.logurl.md) to review cloud logs of your code executing. The [DEBUG](#debug-environment-variable) environment variable can be useful to see verbose output as well.
 
 5. Next, run a sample of your workload through [cost analyzer](./api/faastjs.costanalyzer.md) to find a good cost-performance tradeoff for the choice of memory size. A good default choice for CPU or S3-bandwidth bound workloads is between 1728MV-2048MB on AWS.
 

docs/02-development-workflow.md

@@ -83,7 +83,7 @@ Cost estimates are estimates. They do not capture all costs, and you should not
 
 -   The estimates do not take into account free tiers.
 
--   The estimates assume worst-case tier pricing. If your cloud usage is extensive you may qualify for lower priced tiers (however AWS Lambda and Google Cloud Functions currently do not have tiered pricing, and usually account for most of the cost of faast.js workloads).
+-   The estimates assume worst-case tier pricing. If your cloud usage is extensive you may qualify for lower priced tiers (however AWS Lambda currently do not have tiered pricing, and usually account for most of the cost of faast.js workloads).
 
 -   Ongoing storage costs such as S3 storage are not counted because they are ongoing and not ephemeral.
 

docs/03-cost-estimates.md

@@ -12,8 +12,6 @@ Running programs at scale introduce new issues. This topic covers some of these
 
 AWS Lambda has documented [limits](https://docs.aws.amazon.com/lambda/latest/dg/limits.html). In particular, the default concurrency limit for lambda invocations is 1000 per account. This limit can be increased by request.
 
-Google Cloud Functions has several [quotas](https://cloud.google.com/functions/quotas).
-
 ## Tail latency
 
 When running hundreds or thousands of requests, it is not uncommon that a small number of requests hit a bottleneck, such as network congestion or storage system lags. If even 0.1% of requests takes a very long time, then a job with 1000 concurrent invocations can be held up even if almost all of the work is finished.

docs/05-google-cloud.md

@@ -20,4 +20,4 @@ The cost analyzer takes a [`Workload`](./api/faastjs.costanalyzer.workload.md) a
 
 ## Implementing Providers
 
-Review the implementation for the [AWS](../src/aws/aws-faast.ts) and [Google](../src/google/google-faast.ts) to understand the Provider API.
+Review the implementation for the [AWS](../src/aws/aws-faast.ts) to understand the Provider API.

docs/07-throttling-scaling.md

@@ -43,10 +43,6 @@ Arguments and return values are sent through each provider's API or through a cl
 
 Limits for AWS Lambda are published [here](https://docs.aws.amazon.com/lambda/latest/dg/limits.html). These limits manifest differently for [https vs queue mode](./04-aws.md#queue-vs-https-mode).
 
-### Google Limits
-
-Limits for Google Cloud Functions are published [here](https://cloud.google.com/functions/quotas). As of March 2019 the limits are for arguments and return values is 10MB.
-
 ### Local limits
 
 In local mode, faast.js uses node's [`process.send()`](https://nodejs.org/api/process.html#process_process_send_message_sendhandle_options_callback) to send messages to worker processes. The IPC limits are OS-specific.