Google Cloud Functions enables users to run code in the cloud with no servers or containers to manage. Cloud Functions is a scalable, pay-as-you-go functions as a service (FaaS) product to help build and connect event driven services with simple, single purpose code.
N/A
Google Kubernetes Engine
Score 8.1 out of 10
N/A
Google Kubernetes Engine supplies containerized application management powered by Kubernetes which includes Google Cloud services including load balancing, automatic scaling and upgrade, and other Google Cloud services.
$0.04
vCPU-hr Autopilot Mode
Pricing
Google Cloud Functions
Google Kubernetes Engine
Editions & Modules
No answers on this topic
Autopilot Mode - 3 year commitment price (USD)
$0
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0000438
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Regular Price
$0.0000548
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Spot Price
$0.0000548
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Spot Price
$0.0014767
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - 3 year commitment price (USD)
$0
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0039380
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - Regular Price
$0.0049225
GKE Autopilot Price GB-hr
Autopilot Mode - Spot Price
$0.0133
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - 3 year commitment price (USD)
$0.02
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0356000
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - Regular Price
$0.0445
vCPU Price vCPU-hr
Standard Mode
$0.10
per hour
Cluster Management
$0.10
per cluster per hour
Cluster Management
$74.40 monthly credit
per month per hour
Standard Mode - Free Version
Free
per hour
Offerings
Pricing Offerings
Google Cloud Functions
Google Kubernetes Engine
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google Cloud Functions
Google Kubernetes Engine
Features
Google Cloud Functions
Google Kubernetes Engine
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
It is easy to use, in 15 minutes you just have to follow a few steps, do some easy configurations and you have the project ready to run, once it is connected to the codebase, the execution is automatic. For anyone coming into the google environment, Functions make code execution easy and transparent. CI/CD is perfect
If your application is complex, if it's planet-scale, or if you need autoscaling, then Kubernetes is best suited. If your application is straightforward, you can opt for App Engine or Cloud Run. In many cases, you can prefer to run the cloud on GKE. But once you deploy on Kubernetes, you get the flexibility to try different things. But if you don't seek flexibility, it's not an option for you.
Engine upgrade rollout strategy - well documented and configurable
Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)
Overall Google Cloud Functions is losing a lot of benefits to other GCP services, making it less attractive to users. A simple example would be the need to zip application files and push them to Google Storage which makes it a bit complicated to automate via a CI/CD pipeline. Another "similar" solution would be using Cloud Run although the need for a docker image is there, with the recent evolutions to Cloud Run (ability to downscale to 0) it makes a lot more interesting.
Documentation is provided and clear for this service. Although GCP support is included in the current contract we didn't get to use it since the process is pretty straightforward.
Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.
It is easier to keep everything in house when we are using GCP or AWS. To mix Lambda with google cloud is not a best practice and will cause problems ahead. The segmentation is clear, if you are using google, you use Google Cloud Functions. if you are on Amazon, you use all AWS tools. You can't mix them. The price is set.
GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.
When issues came up, we reached out to some folks at GCP and they seemed to be very prompt and attentive to our needs. They were always willing to help and provide additional details or recommendations or links to resources. This kind of support is very helpful as it allows us to navigate GKE with more confidence.