agentsclimarketplace

Resonate http service design typescript

Skill resonatehq/resonate-skills/resonate-http-service-design-typescript

Design HTTP services that use Resonate durable functions behind route handlers, including routing patterns, workflow boundaries, and RPC calls to other service workers (e.g., database service). Use when building or refactoring HTTP APIs that trigger durable workflows in TypeScript.From its SKILL.md

Install
npx -y skills add resonatehq/resonate-skills --skill resonate-http-service-design-typescript

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.4 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Resonate HTTP Service Design

SDK version: This skill reflects @resonatehq/sdk v0.11.2 (current on npm).

Overview

Use this skill to design HTTP services where route handlers start or await durable workflows. The HTTP server is the entrypoint; durable functions do the work and coordinate via Resonate. Downstream services (like a database service) expose their own durable functions and are invoked via RPC.

Architecture Model

  • HTTP service: Express/Fastify server handling routes and mapping requests to durable workflows.
  • Worker service: Resonate worker group that runs durable functions for business logic.
  • DB service: Separate worker group exposing durable DB functions via Resonate RPC.
  • Resonate Server: Durable promise store and coordination hub.
client -> HTTP routes -> Resonate Client (beginRpc/run)
         -> worker group (durable workflow)
             -> ctx.rpc -> db worker group (durable db functions)

Rules

  • Route handlers are ephemeral: use Resonate Client APIs, not Context APIs.
  • Durable functions are generator functions: function* with yield*.
  • All external effects occur in durable steps and are awaited or explicitly detached.
  • Use stable promise IDs for idempotency and replay safety.

Route Design Patterns

1) Submit and poll (async HTTP)

  • POST /jobs starts a workflow and returns jobId.
  • GET /jobs/:id returns status or result.

2) Submit and callback

  • POST /jobs starts a workflow and returns jobId.
  • External system resolves a promise when done.

3) Webhook gate

  • POST /webhooks/service resolves a durable promise tied to a workflow.

Code Examples

HTTP server entrypoints (Express)

import express from "express";
import { Resonate } from "@resonatehq/sdk";
import crypto from "node:crypto";

const app = express();
app.use(express.json());

const resonate = new Resonate({
  url: "http://localhost:8001",
  group: "api",
});

// Start workflow
app.post("/jobs", async (req, res) => {
  const jobId = `job/${crypto.randomUUID()}`;

  await resonate.beginRpc(
    jobId,
    "process-job",
    req.body,
    resonate.options({ target: "poll://any@workers" })
  );

  res.status(202).json({ id: jobId });
});

// Poll status
app.get("/jobs/:id", async (req, res) => {
  const handle = await resonate.get(req.params.id);
  const result = await handle.result();
  res.json({ id: req.params.id, result });
});

// Webhook: external system resolves promise
app.post("/webhooks/approval", async (req, res) => {
  const { promiseId, approved } = req.body;
  const data = Buffer.from(JSON.stringify({ approved })).toString("base64");
  await resonate.promises.resolve(promiseId, { data });
  res.status(204).end();
});

Worker service (durable workflow)

import { Resonate, type Context } from "@resonatehq/sdk";

const resonate = new Resonate({ url: "http://localhost:8001", group: "workers" });

function* processJob(ctx: Context, payload: { accountId: string }) {
  const account = yield* ctx.rpc(
    "db.getAccount",
    payload.accountId,
    ctx.options({ target: "poll://any@db" })
  );

  const result = yield* ctx.run(processAccount, account);

  const approval = yield* ctx.promise({ id: `approve/${ctx.id}` });
  const ok = yield* approval as boolean;
  if (!ok) {
    throw new Error("rejected");
  }

  yield* ctx.rpc(
    "db.saveResult",
    { id: ctx.id, result },
    ctx.options({ target: "poll://any@db" })
  );

  return { status: "done", result };
}

resonate.register("process-job", processJob);

DB service (durable database functions)

import { Resonate, type Context } from "@resonatehq/sdk";

const resonate = new Resonate({ url: "http://localhost:8001", group: "db" });

function* getAccount(_: Context, id: string) {
  return await db.loadAccount(id);
}

function* saveResult(_: Context, record: { id: string; result: unknown }) {
  await db.save(record);
  return { ok: true };
}

resonate.register("db.getAccount", getAccount);
resonate.register("db.saveResult", saveResult);

Determinism Notes

  • Use ctx.date.now() and ctx.math.random() inside durable functions.
  • Wrap side effects in durable steps (ctx.run, ctx.rpc).
  • Ensure returned objects are serializable.

Structured Concurrency Example

function* aggregate(ctx: Context, ids: string[]) {
  const futures = ids.map((id) =>
    ctx.beginRpc("db.getAccount", id, ctx.options({ target: "poll://any@db" }))
  );

  const results = [];
  for (const f of futures) {
    results.push(yield* f);
  }

  return results;
}

Error Handling

  • Throw errors for normal failures; Resonate retries by default.
  • Use ctx.options({ timeout: ... }) to bound retries.
  • Treat 40900 (promise exists) as idempotency, not failure.

Promise ID Strategy

  • Use request-derived IDs for idempotency, or generate UUIDs for fire-and-forget.
  • Keep IDs readable: job/<uuid>, approve/<jobId>, db/op/<jobId>.

Route Checklist

  • Inputs validated and serialized before RPC.
  • Durable workflow entrypoint registered and reachable.
  • Target group matches worker group name.
  • Promise ID uniqueness guaranteed.
  • Routes return 202 + ID for async workflows.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.