Bounda on Cloudflare

An event-sourced app on Bounda, running on Cloudflare: one Worker and one Durable Object per tenant, with the events, the read models and the scheduled work in the object's own SQLite. Nothing else to run.

Every command is appended as an event and projected into a read model before the request answers, so a query right after a command sees it. The page at / places orders and lists them through the JSON API.

The same project comes out of npm create bounda@latest my-app -- --runtime cloudflare; this repository is generated from it on every release.

npm install
npm test             # the app and its API, inside workerd
npm run test:e2e     # the page against wrangler dev, in Playwright
npm run dev          # wrangler dev on http://localhost:8787
npm run deploy       # wrangler deploy, to your Cloudflare account

Every script first runs bounda generate, which writes the typed registry under .bounda/ and a +types/ folder next to each module; run it yourself after adding a module, so your editor sees its types. dev, typecheck and check also run wrangler types, which writes worker-configuration.d.ts from wrangler.jsonc.

Open http://localhost:8787 once dev is running: public/index.html places orders and lists them through the API. Or from a terminal:

curl -X POST localhost:8787/commands/placeOrder \
  -H 'content-type: application/json' -H 'x-bounda-tenant: acme' \
  -d '{"orderId":"018f6a5e-4c3c-7c1e-9d4b-0b2c4a1d8e01","customerId":"ada","total":42}'
curl -X POST localhost:8787/queries/listOrders \
  -H 'content-type: application/json' -H 'x-bounda-tenant: acme' \
  -d '{"customerId":"ada"}'

Where things go

app/domain/order/           the order aggregate
app/read/orders/            a read model
bounda.config.ts            storage: cloudflare()
src/worker.ts               the Durable Object class and the HTTP API
public/index.html           a page that uses the API, served as a static asset
wrangler.jsonc              the binding and the SQLite migration for the object
tests/orders.test.ts        the domain, on an in-memory store
tests/api.test.ts           the API, against the Durable Object in workerd
e2e/demo.spec.ts            the page, end to end

src/worker.ts uses createWorker, a JSON API with no authentication: a starting point. An app with users writes its own fetch and talks to its store with connect(stub), which types commands and queries from your modules. Each tenant is its own object; x-bounda-tenant picks it, default without the header.

.bounda/ and +types/ are generated; they stay out of git.