Specifically, as we have already mention, this article will be dicat to explaining how to perform this extraction via API using Cloud Functions.
What do we know about Cloud Functions?
Let’s remember: Cloud Functions is a serverless code execution environment that Google makes available to us within the range of Google Cloud tools and resources. It allows us to develop functions and deploy them (almost) instantly, as of today, in the following programming languages: .NET, Go, Java, Node.js, PHP, Python and Ruby.
How exactly does it work?
When we want to deploy our function, Google compiles it and every time we call it (using some of the mechanisms that Google makes available viber database to us to do so), the Cloud Functions environment invokes it, it runs for a maximum time and ends.
Cloud Functions allows us
To configure our functions to use a certain amount of RAM, adjust the processing power with a defin number of CPUs (or a fraction if the function is very small), its concurrency level, the security level, the trigger type (the way our function after finding the answers to these questions can be invok) and some more parameters.
This allows us to create a very flexible range of functions that adapt to our nes without too many complications.
What can we do?
You can develop all kinds of functions (or applications) with Cloud Functions, from microservices to more complex applications. Google provides us with a wide variety of third-party libraries to complement the programming language we choose tg data for development. Microservices? Of course. The Internet of Things? Of course. Data extraction, transformation and/or loading? No problem!
While it’s not entirely practical
To spin up very. Does it have any limits? large functions (since the whole idea behind Cloud Functions is to launch relatively small processes repeatly) there aren’t too many limits as to what you can do.