How jasonpraful/hono-workflows-do works
Project type and purpose
• This is a serverless microservices project built on Cloudflare Workers.
• It consists of two worker scripts:
– A “core” Hono‑based HTTP API + Web UI (JSX) that exposes OpenAPI/Swagger, triggers workflows, and displays their status.
– A “workflows” worker that executes asynchronous processes (timer, AI image generation) and pushes results to R2.
• Durable Objects store workflow state; R2 stores generated images; external AI API generates images.
File structure
• Top‑level:
– README.md, bun.lock, package.json, tsconfig.json, .prettierrc
• functions/core:
– src/routes: HTTP handlers for /ai, /image, /state, /timer
– src/ui: Hono‑JSX components (CreatePost, Post, Layout) for the browser UI
– src/middleware: Durable Objects binding, cross‑script calls
– workflows.ts: cross‑script client to call the workflows worker
– wrangler.jsonc + package.json: binding definitions, dev scripts
• functions/workflows:
– src/index.ts: entry point; routes to ai.ts (calls external AI, writes R2), timer.ts (timer logic)
– wrangler.jsonc + package.json: separate worker config
README for additional insights
• The core service exposes OpenAPI + Swagger UI.
• Workflows include Timer and AI flows, triggered via HTTP from core.
• Cross‑script calls and Durable Object usage are key gaps in Cloudflare docs this demo fills.
Elements
– API/workers in another (e.g., green)
– Storage/state in another (e.g., orange)
– External services in gray