Limits
Fleet's serverless technology is designed to be faster and more secure.
We continue with two premises to create Fleet, we must build a serverless technology that performs functions much faster than other platforms and that is safe.
We decided to adopt Node.js as a basis to enable developers to bring their existing functions from other serverless platforms to ours and continue in the ecosystem. But for that to happen we had to limit access to some APIs available from Node.js in the context of the function for security purposes. You can see below the list of unavailable Node.js API's.
Isolates
Learn how Fleet's serverless technology works.
Unavailable APIs
In addition to the native Node.js modules that we disable in the context of the function, some methods are unavailable.
eval()is not allowed for security reasons.new Functionis not allowed for security reasons.
Limited APIs
In addition to the unavailable APIs, there are some restrictions for some available APIs. Some of its methods are limited for security purposes and it is very unlikely that you will need these APIs because Fleet will take care of this for you.
Resource Limits
The following limits apply to role configuration, deployments, and execution. They cannot be changed.
| Resource | Limit |
|---|---|
| Deployment Package Size | 25 MB (compressed, for direct upload) |
| Threads | 1 |
| Function Environment Variables | 4 KB |
| Function timeout | 300 seconds (5 minutes) |
| Maximum gateway timeout | 120 seconds (2 minutes) |
| Function Memory Allocation | 128 MB Soon more sets |
| Body length | 10 MB |
CPU capacity and other resources are allocated proportionately. The amount of memory is proportional to the CPU available per function. More memory configurations became available over time.