Although we have mention that there are not too many limits as to what can be done with Cloud Functions, a function has 540 seconds (9 minutes). If any process extends beyond these 9 minutes, the Cloud Functions environment will terminate the execution of our function, whether it has finish or not.
We must take into account
Google Cloud’s philosophy: you only pay for what you use. Depending on the configuration options we have us to create our function, it will have one cost or another (the greater the amount of RAM or number of CPUs available, among other factors, the higher the cost).
In addition, we must add
The cost (if any) of the services we use, whether they are from Google Cloud or from external providers (in our case we will use BigQuery 99 acres database to store data, Cloud Functions for execution and the Search Console API).
That said, let’s get to the interesting part:
2. Our first function with Cloud Functions.
Creating a function with Cloud Functions is quite simple. To do this, we use the hamburger menu locat at the top left of the screen and select the research also shows who the company’s the submenu mark Cloud Functions .Next, we click on the button mark CREATE FUNCTION .
Among the different basic configuration options
The first thing we ne to do is specify the identifying name of our function. We can also specify the Google Cloud region in which the function will be execut (by default it is usually deploy in the Unit States) and the environment in which it will be execut (which, by default and at the time of publishing this article, is execut as a second-generation function).
Next we ne to define the trigger
Type for our function. The default trigger is HTTPS (if we want tg data our function to be accessible from a URL) but we can choose others such as Pub/Sub, Firestore or others. We can copy the URL that appears just below as it is the URL we will access to invoke our function.