Technology guide network for runtimes, frameworks, and data
Continue from Cloudflare platform boundaries into Bun, Deno, TanStack, PostgreSQL, MariaDB, and Valkey, then return to an Orange Book implementation path.
Edited and verified by Orange Book Editorial Team ·
Give each site one job
Orange Book explains how an application enters Cloudflare, how Workers and storage choices fit together, and how to verify production boundaries. The six topic sites go deeper into language runtimes, application frameworks, and data engines. Choose a task here and follow a deep link; you do not need to read every site from beginning to end.
Runtimes and toolchains
Bun: local toolchain versus workerd
Bun can install dependencies, invoke Wrangler, and run tests, while the deployed Worker still executes in workerd. Start with deploying Bun tooling to Cloudflare Workers, then return to Workers Runtime versus Node.js for the compatibility gate.
Deno: Web API model and platform differences
Deno and Workers both emphasize Web APIs, but their permissions, deployment, persistence, and Node compatibility boundaries differ. Read Deno versus Node and Bun before applying the Workers runtime review.
Application framework
TanStack: application and server boundaries
TanStack Start, Router, and Query cover routing, SSR, Server Functions, and server state; Cloudflare supplies the target runtime and platform resources. Use the TanStack ecosystem map to choose tools, then assign platform responsibilities with the complete application layers.
Relational data and the hot path
PostgreSQL: full SQL and production operations
When standard PostgreSQL, extensions, complex transactions, or an existing database matter, begin at the cloud PostgreSQL entry point. After choosing the engine, use the external database overview to select Hyperdrive or an official driver.
MariaDB: MySQL protocol ecosystem and cloud choices
For an existing MariaDB estate or workloads that depend on its engines, replication, and operational ecosystem, begin with MariaDB on the cloud. Before connecting a Worker, verify Hyperdrive TLS, driver, and connection boundaries in the external database overview.
Valkey: cache, sessions, rate limits, and hot data
Valkey is an external in-memory data engine; it is not the same thing as Workers KV or the Cache API. Read Valkey for beginners, then use the Orange Book storage chooser to decide whether built-in platform capabilities are already sufficient.
Recommended reading sequence
- Use Orange Book to define the target runtime, request responsibilities, and data shape.
- Enter one topic site to learn that technology's model, limits, and operations.
- Return to Orange Book for Cloudflare connectivity, secrets, caching, tests, and release verification.
- For APIs, limits, pricing, and compatibility dates, use the Cloudflare primary sources listed on each Orange Book page.
These are related learning resources and do not imply official endorsement by Bun, Deno, TanStack, PostgreSQL, MariaDB, Valkey, or Cloudflare.
Primary sources
Did this page help you complete your goal?
Beta feedback is generated in this browser and is never uploaded automatically.
D1 vs Supabase and Neon: edge SQLite or serverless Postgres
Compare Cloudflare D1, Supabase, and Neon across runtime model, SQL, capacity, consistency, platform scope, and billing dimensions.
Cloudflare AI capability map
Separate Workers AI, Vectorize, AI Gateway, and Agents before composing an AI application.