Skip to content

Packaging DuckDB for Node.js Lambda functions. Example application: https://github.com/tobilg/serverless-duckdb

License

Notifications You must be signed in to change notification settings

SensorUp/duckdb-nodejs-layer

 
 

Repository files navigation

duckdb-nodejs-layer

Packaging DuckDB for usage in AWS Lambda functions with Node.js, and publishing as public Lambda layers.

Usage

You can use the published layers in your own serverless applications by referencing it as outlined in the different framework's docs:

The layers get automatically published to all currently available (in the moment of publishing) AWS regions.

Example usage

You can have a look at the example repository, which uses this AWS Lambda layer: tobilg/serverless-duckdb. More specifically, the src/functions/query.js should give you a good idea on how it can be used.

The recommendation is to use a bundler such as WebPack for the packaging of your application. This means you can locally use (e.g. for testing) the official duckdb npm package (via npm i --save duckdb), but exclude it in the packaging process, because after being deployed to a Lambda function, the updated DuckDB version from the Lambda layer will be used.

Code example

import DuckDB from 'duckdb';

// Instantiate DuckDB
const duckDB = new DuckDB.Database(':memory:');

// Create connection
const connection = duckDB.connect();

// Promisify query method
const query = (query) => {
  return new Promise((resolve, reject) => {
    connection.all(query, (err, res) => {
      if (err) reject(err);
      resolve(res);
    })
  })
}

// Will show DuckDB version
await query(`PRAGMA version;`);

DuckDB layer

This contains a AWS Lambda layer in different flavors, both x86 and arm64 architectures are supported.

The ARNs follow the following logic:

arn:aws:lambda:$REGION:041475135427:layer:duckdb-nodejs-$ARCHITECTURE:$VERSION

where $ARCHITECTURE can have the following values:

  • x86
  • arm64

Enabled extensions

The following DuckDB default extensions are enabled and contained in the static build:

  • parquet: Adds support for reading and writing parquet files
  • httpfs: Adds support for reading and writing files over a HTTP(S) connection
  • json: Adds support for JSON operations
  • fts: Adds support for Full-Text Search Indexes
  • icu: Adds support for time zones and collations using the ICU library

x86 layer ARNs

Layer version to DuckDB version mapping:

Layer version DuckDB version
3 v0.8.0
4 v0.8.1
5 v0.9.0
6 v0.9.1
7 v0.9.2
8 v0.10.0
9 v0.10.1

The ARNs of the latest x86 version of the DuckDB Node.js Lambda layer are:

Region Layer ARN
af-south-1 arn:aws:lambda:af-south-1:041475135427:layer:duckdb-nodejs-x86:9
ap-east-1 arn:aws:lambda:ap-east-1:041475135427:layer:duckdb-nodejs-x86:9
ap-northeast-1 arn:aws:lambda:ap-northeast-1:041475135427:layer:duckdb-nodejs-x86:9
ap-northeast-2 arn:aws:lambda:ap-northeast-2:041475135427:layer:duckdb-nodejs-x86:9
ap-northeast-3 arn:aws:lambda:ap-northeast-3:041475135427:layer:duckdb-nodejs-x86:9
ap-south-1 arn:aws:lambda:ap-south-1:041475135427:layer:duckdb-nodejs-x86:9
ap-south-2 arn:aws:lambda:ap-south-2:041475135427:layer:duckdb-nodejs-x86:9
ap-southeast-1 arn:aws:lambda:ap-southeast-1:041475135427:layer:duckdb-nodejs-x86:9
ap-southeast-2 arn:aws:lambda:ap-southeast-2:041475135427:layer:duckdb-nodejs-x86:9
ap-southeast-3 arn:aws:lambda:ap-southeast-3:041475135427:layer:duckdb-nodejs-x86:9
ap-southeast-4 arn:aws:lambda:ap-southeast-4:041475135427:layer:duckdb-nodejs-x86:9
ca-central-1 arn:aws:lambda:ca-central-1:041475135427:layer:duckdb-nodejs-x86:9
eu-central-1 arn:aws:lambda:eu-central-1:041475135427:layer:duckdb-nodejs-x86:9
eu-central-2 arn:aws:lambda:eu-central-2:041475135427:layer:duckdb-nodejs-x86:9
eu-north-1 arn:aws:lambda:eu-north-1:041475135427:layer:duckdb-nodejs-x86:9
eu-south-1 arn:aws:lambda:eu-south-1:041475135427:layer:duckdb-nodejs-x86:9
eu-south-2 arn:aws:lambda:eu-south-2:041475135427:layer:duckdb-nodejs-x86:9
eu-west-1 arn:aws:lambda:eu-west-1:041475135427:layer:duckdb-nodejs-x86:9
eu-west-2 arn:aws:lambda:eu-west-2:041475135427:layer:duckdb-nodejs-x86:9
eu-west-3 arn:aws:lambda:eu-west-3:041475135427:layer:duckdb-nodejs-x86:9
me-central-1 arn:aws:lambda:me-central-1:041475135427:layer:duckdb-nodejs-x86:9
me-south-1 arn:aws:lambda:me-south-1:041475135427:layer:duckdb-nodejs-x86:9
sa-east-1 arn:aws:lambda:sa-east-1:041475135427:layer:duckdb-nodejs-x86:9
us-east-1 arn:aws:lambda:us-east-1:041475135427:layer:duckdb-nodejs-x86:9
us-east-2 arn:aws:lambda:us-east-2:041475135427:layer:duckdb-nodejs-x86:9
us-west-1 arn:aws:lambda:us-west-1:041475135427:layer:duckdb-nodejs-x86:9
us-west-2 arn:aws:lambda:us-west-2:041475135427:layer:duckdb-nodejs-x86:9

arm64 layer ARNs

Layer version to DuckDB version mapping:

Layer version DuckDB version
1 v0.8.0
2 v0.8.1
3 v0.9.0
4 v0.9.1
5 v0.9.2
6 v0.10.0
7 v0.10.1

The ARNs of the latest arm64 version of the DuckDB Node.js Lambda layer are:

Region Layer ARN
us-east-1 arn:aws:lambda:us-east-1:041475135427:layer:duckdb-nodejs-arm64:7
us-east-2 arn:aws:lambda:us-east-2:041475135427:layer:duckdb-nodejs-arm64:7
us-west-1 arn:aws:lambda:us-west-1:041475135427:layer:duckdb-nodejs-arm64:7
us-west-2 arn:aws:lambda:us-west-2:041475135427:layer:duckdb-nodejs-arm64:7
af-south-1 arn:aws:lambda:af-south-1:041475135427:layer:duckdb-nodejs-arm64:7
ap-east-1 arn:aws:lambda:ap-east-1:041475135427:layer:duckdb-nodejs-arm64:7
ap-southeast-3 arn:aws:lambda:ap-southeast-3:041475135427:layer:duckdb-nodejs-arm64:7
ap-south-1 arn:aws:lambda:ap-south-1:041475135427:layer:duckdb-nodejs-arm64:7
ap-northeast-3 arn:aws:lambda:ap-northeast-3:041475135427:layer:duckdb-nodejs-arm64:7
ap-northeast-2 arn:aws:lambda:ap-northeast-2:041475135427:layer:duckdb-nodejs-arm64:7
ap-southeast-1 arn:aws:lambda:ap-southeast-1:041475135427:layer:duckdb-nodejs-arm64:7
ap-southeast-2 arn:aws:lambda:ap-southeast-2:041475135427:layer:duckdb-nodejs-arm64:7
ap-northeast-1 arn:aws:lambda:ap-northeast-1:041475135427:layer:duckdb-nodejs-arm64:7
ca-central-1 arn:aws:lambda:ca-central-1:041475135427:layer:duckdb-nodejs-arm64:7
eu-central-1 arn:aws:lambda:eu-central-1:041475135427:layer:duckdb-nodejs-arm64:7
eu-west-1 arn:aws:lambda:eu-west-1:041475135427:layer:duckdb-nodejs-arm64:7
eu-west-2 arn:aws:lambda:eu-west-2:041475135427:layer:duckdb-nodejs-arm64:7
eu-south-1 arn:aws:lambda:eu-south-1:041475135427:layer:duckdb-nodejs-arm64:7
eu-west-3 arn:aws:lambda:eu-west-3:041475135427:layer:duckdb-nodejs-arm64:7
eu-north-1 arn:aws:lambda:eu-north-1:041475135427:layer:duckdb-nodejs-arm64:7
me-south-1 arn:aws:lambda:me-south-1:041475135427:layer:duckdb-nodejs-arm64:7
sa-east-1 arn:aws:lambda:sa-east-1:041475135427:layer:duckdb-nodejs-arm64:7

x86_64 layer with arrow, aws and httpfs extensions ARNs

This layer contains the arrow, aws and httpfs extensions. This enables Lambda functions that are in a VPC and have no internet access to download these extensions via HTTP (e.g. from extensions.quacking.cloud) for cost savings.

VPC access is for example necessary if you want your Lambda functions to access S3 Express One Zone. You can have a look at how to deploy such kind of setup in the tobilg/serverless-duckdb repo.

Currently, it's only available in us-east-1.

Layer version to DuckDB version mapping:

Layer version DuckDB version
1 v0.10.0
2 v0.10.1

The ARNs of the latest x86_64 version of the DuckDB Node.js Lambda layer with extensions are:

Region Layer ARN
us-east-1 arn:aws:lambda:us-east-1:041475135427:layer:duckdb-extensions-nodejs-x86:2

About

Packaging DuckDB for Node.js Lambda functions. Example application: https://github.com/tobilg/serverless-duckdb

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 36.5%
  • Shell 33.0%
  • CMake 24.0%
  • Makefile 4.8%
  • JavaScript 1.7%