Google Cloud Functions vs Fermyon Cloud
Compare Service Types, Runtimes, Execution Limits, Compliance, Regions and Alternatives
Features
Google Cloud Functions
Service Types
Functions
Containers
Database
PaaS
N/A
Edge Compute
Fermyon Cloud
Service Types
Functions
Containers
Database
PaaS
Edge Compute
Google Cloud Functions
Supported Containers
Docker
Fermyon Cloud
Supported Containers
Docker
Google Cloud Functions
Supported Runtimes
.NET Core
AssemblyScript
C
C#
C++
Clojure
Erlang
Go
Grain
Haskell
Java
JavaScript
Kotlin
Motoko
Node.js
PHP
Python
Ruby
Rust
Scala
Swift
TypeScript
Wasm
Zig
Fermyon Cloud
Supported Runtimes
.NET Core
AssemblyScript
C
C#
C++
Clojure
Erlang
Go
Grain
Haskell
Java
JavaScript
Kotlin
Motoko
Node.js
PHP
Python
Ruby
Rust
Scala
Swift
TypeScript
Wasm
Zig
Google Cloud Functions
Execution Limits and Resource Quotas
Min. Memory
128 MB
Max. Memory
8 GB / 32 GiB
Default Timeout
60 sec
Max. Timeout
9 min / 60 min
Request Payload
10 MB / 32 MB
Response Payload
10 MB / 32 MB
Fermyon Cloud
Execution Limits and Resource Quotas
Min. Memory
128 MB
Max. Memory
32 GB
Default Timeout
30 sec
Max. Timeout
5 min
Request Payload
1 MB
Response Payload
1 MB
Google Cloud Functions
Compliance
IDW PS 880
ISAE 3000
ISAE 3402
ISO 20000-1
ISO 27001
ISO 27018
ISO 9001
WACA
Fermyon Cloud
Compliance
IDW PS 880
ISAE 3000
ISAE 3402
ISO 20000-1
ISO 27001
ISO 27018
ISO 9001
WACA
Google Cloud Functions
Regional Availability
Deployment Scope
Regional
Regions
NA, LATAM, EU, APAC
Points of Presence
23 / 40
Fermyon Cloud
Regional Availability
Deployment Scope
1
Regions
N/A
Points of Presence
N/A
Alternatives are matched on service types, programming languages and container support
