At first, those terms confused me as well. vCPU-seconds and GB-seconds are calculated from what kind of machine on what you want to deploy and how long it takes to compute (total second per month, of course).
For example, if you specified each machine to have 2 CPU cores with 1GB of RAM. And it serves for 150,000 seconds (counted only when it's processing something, which means you will not be billed when no one is making requests). That will be counted as 150,000 GB-seconds and 300,000 vCPU-seconds which is safely under the free quotas.
Requests is just the number of requests. and GB egress is the amount of out-going data.
When it comes to estimating the price for Google services, I always find this Pricing Calculator helpful! (like a lot)
hope this helps
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Google Cloud Run + Cloud Datastore might be what you're looking for.
At this point, it may be GCP vs AWS. Maybe I am concerned too much about the pricing...
What does it even mean?
At first, those terms confused me as well. vCPU-seconds and GB-seconds are calculated from what kind of machine on what you want to deploy and how long it takes to compute (total second per month, of course).
For example, if you specified each machine to have 2 CPU cores with 1GB of RAM. And it serves for 150,000 seconds (counted only when it's processing something, which means you will not be billed when no one is making requests). That will be counted as 150,000 GB-seconds and 300,000 vCPU-seconds which is safely under the free quotas.
Requests is just the number of requests. and GB egress is the amount of out-going data.
When it comes to estimating the price for Google services, I always find this Pricing Calculator helpful! (like a lot)
hope this helps