denoland/celldPublic

self-hosted, distributed Durable Objects

v0.3.0

github-actions[bot]bot published 89e4ffcImmutable

Release notes

- v0.3.0 adds a replicated write-behind log. Fleets of two or more nodes acknowledge writes after peer fsync while bucket upload finishes later. In testing, this delivers 10× lower write latency and over 100× fewer Class A S3 operations. A v0.2.1 fleet can roll forward one node at a time.

- Added support for Azure Blob Storage (`az://<BUCKET_NAME>`).

- Added support for D1 databases, including the `celld d1` CLI for migrations and SQL execution.

- Added support for cron triggers, with durable fleet-wide scheduling, retries for failed handlers, and recovery of one missed run after downtime.

- Streaming and rewrapping request bodies are up to 70× faster, and text decoding is up to 44× faster.

- WebSocket upgrades now work correctly for Durable Object subrequests and cross-script service bindings.

- `setInterval()` now works correctly.

- `celld deploy` now accepts Node built-in specifiers (E.G. `node:util`)

- Each isolate now has a configurable V8 heap limit. celld refuses new hibernatable WebSockets and oversized SQL materialization near that limit, then resumes service after memory use falls.

- Correctness fixes prevent overlapping alarm handlers, events from resuming in freed isolates, lost transactions at replication segment boundaries, and database corruption after eviction and reactivation.

- Closed issues: [#139](https://github.com/denoland/celld/issues/139), [#144](https://github.com/denoland/celld/issues/144), [#147](https://github.com/denoland/celld/issues/147), [#149](https://github.com/denoland/celld/issues/149), [#150](https://github.com/denoland/celld/issues/150), [#152](https://github.com/denoland/celld/issues/152), [#154](https://github.com/denoland/celld/issues/154), [#155](https://github.com/denoland/celld/issues/155), [#156](https://github.com/denoland/celld/issues/156), [#157](https://github.com/denoland/celld/issues/157), and [#158](https://github.com/denoland/celld/issues/158).

Attached at publication

- v0.3.0 adds a replicated write-behind log. Fleets of two or more nodes acknowledge writes after peer fsync while bucket upload finishes later. In testing, this delivers 10× lower write latency and over 100× fewer Class A S3 operations. A v0.2.1 fleet can roll forward one node at a time.

- Added support for Azure Blob Storage (`az://<BUCKET_NAME>`).

- Added support for D1 databases, including the `celld d1` CLI for migrations and SQL execution.

- Added support for cron triggers, with durable fleet-wide scheduling, retries for failed handlers, and recovery of one missed run after downtime.

- Streaming and rewrapping request bodies are up to 70× faster, and text decoding is up to 44× faster.

- WebSocket upgrades now work correctly for Durable Object subrequests and cross-script service bindings.

- `setInterval()` now works correctly.

- `celld deploy` now accepts Node built-in specifiers (E.G. `node:util`)

- Each isolate now has a configurable V8 heap limit. celld refuses new hibernatable WebSockets and oversized SQL materialization near that limit, then resumes service after memory use falls.

- Correctness fixes prevent overlapping alarm handlers, events from resuming in freed isolates, lost transactions at replication segment boundaries, and database corruption after eviction and reactivation.

- Closed issues: [#139](https://github.com/denoland/celld/issues/139), [#144](https://github.com/denoland/celld/issues/144), [#147](https://github.com/denoland/celld/issues/147), [#149](https://github.com/denoland/celld/issues/149), [#150](https://github.com/denoland/celld/issues/150), [#152](https://github.com/denoland/celld/issues/152), [#154](https://github.com/denoland/celld/issues/154), [#155](https://github.com/denoland/celld/issues/155), [#156](https://github.com/denoland/celld/issues/156), [#157](https://github.com/denoland/celld/issues/157), and [#158](https://github.com/denoland/celld/issues/158).

Assets 0
None were attached at publication.
No assets.

Shipped in this Release 0

None

Deployments 0

  • None

History 0

No Decisions yet.