Skip to content
nimbus

DynamoDB example apps

A runnable DynamoDB app that builds on Nimbus with the stock @aws-sdk/client-dynamodb client. The @nimbus/dynamodb helper supplies the endpoint, region, and credentials; everything else is the unchanged AWS SDK API. Read the overview first if you have not pointed an AWS SDK at Nimbus yet.

The example lives under examples/dynamodb/ in the source repository. Run it in place from a checkout.

Run the example

Section titled “Run the example”
Terminal window
nimbus dev

nimbus dev starts a local server with the DynamoDB listener on its own endpoint (127.0.0.1:8000 by default) and, when it detects the AWS SDK dependency, writes the NIMBUS_DYNAMODB_* connection variables to .env.local. The access key id selects the Nimbus tenant. Then run the example app from its directory (see its README); it reads those variables and drives the DynamoDB endpoint directly — there is no Nimbus function bundle to deploy.

The app

Section titled “The app”

Tasks is a headless task list against the DynamoDB endpoint. It creates a tasks table with a single string partition key, id, then drives the shared tasks spec through standard AWS SDK commands:

  • PutItem creates an incomplete task with a stable id and creation time.
  • Scan reads every task; because a scan is unordered, the app sorts the results client-side by createdAt, newest first.
  • UpdateItem toggles a task’s completed flag.
  • DeleteItem removes a task.

Live updates are polled

Section titled “Live updates are polled”

DynamoDB has no live-query view on this surface, so the app cannot meet the spec’s no-polling subscription behavior. It satisfies the live-update flow by re-scanning tasks until a later read observes the change. This is polling, not a live subscription — the example records that gap directly rather than emulate one.