Functions Microservice

• Set NPM_CONFIG_REGISTRY to point to your own registry
• Or set the workspace disableNpmRegistry option to true to prevent any runtime npm install entirely (only pre-installed shared packages will be available)

​

Default PYTHON_BUILTIN_MODULES

​

Default NODEJS_SHARED_PACKAGES_WHITELIST_IMPORT

• Every function is treated as if it had the async keyword
• When calling functions from the same workspace, you must use the await keyword
• Results are always returned as promises

// This simple function is still executed asynchronously
function simpleCalc() {
  return 42;
}

// When calling from another function, use await
async function useCalc() {
  const result = await simpleCalc();
  return `The answer is ${result}`;
}

• Functions to call each other directly
• Shared utility functions across the workspace
• Code reuse and modularization

return "world";

return "hello " + (await funcA());

• The cache object persists between function executions
• Use it to store and retrieve values across multiple calls
• Useful for maintaining state or caching expensive operations

let counter = cache['counter']

counter = (counter || 0) + 1

cache['counter'] = counter;

return counter;

let counter = cache['counter'];
return "Counter: " + counter;

• NodeJS functions can use NPM packages. Dependencies are resolved in the following order:
  1. Shared dependencies (pre-installed at build time): A set of commonly needed packages are bundled in the Docker image under SHARED_NODE_MODULES_DIRECTORY and available to all workspaces instantly, without any npm install at runtime. These include packages like lodash, axios, dayjs, mongodb, redis, sharp, and more.
  2. Per-workspace dependencies: Any additional package required by a workspace’s custom code that is not in the shared dependencies will be automatically installed via npm when the function is created or updated. This can be disabled per workspace with the disableNpmRegistry option.
• Python functions can use PyPI packages that have been whitelisted and pre installed with the corresponding environment variables

{
  "functions": {
    "processData": {
      "code": "const _ = require('lodash'); return _.groupBy(data, 'category');",
      "parameters": {
        "data": {
          "type": "array"
        }
      }
    }
  }
}

• Invalid function code syntax
• Unavailable or incompatible dependencies
• Insufficient disk space for dependencies
• Network issues preventing access to the NPM registry

1. Check the service logs for specific error messages
2. Verify NPM registry access from within the container
3. Ensure sufficient disk space in the function storage volume
4. Validate function syntax before submission

• Function code contains infinite loops or excessive processing
• Timeout setting is too low for the operation
• External service calls that take too long

1. Review function code for inefficiencies or infinite loops
2. Adjust the FUNCTIONS_RUN_TIMEOUT or PYTHON_FUNCTIONS_RUN_TIMEOUT setting
3. Implement better error handling for external service calls
4. Consider breaking complex operations into smaller, chainable functions

• Functions attempting to use more memory than allowed
• Memory leaks in long-running functions
• Too many function workers in memory

1. Adjust NODE_WORKER_MAX_OLD_GENERATION_SIZE_MB for larger memory requirements
2. Reduce FUNCTIONS_WORKERS_MAX_LRU if overall memory usage is too high
3. Optimize function code to use less memory
4. Check for and fix memory leaks in function code