Architecture Intermediate March 15, 2026 4 min read

Replatforming a Portfolio Backend to Workers with Hono

How the portfolio backend was reshaped around Cloudflare Workers, Hono, and shared contracts without carrying legacy server complexity forward.

Published

March 15, 2026

Updated

March 15, 2026

Reading time

4 min read

Status

PUBLISHED

cloudflareworkershonoarchitecture

Replatforming a Portfolio Backend to Workers with Hono

Moving a portfolio backend to Cloudflare Workers is mostly a simplification exercise. The goal is not to preserve every server pattern from a traditional Node runtime, but to preserve product behavior while reducing operational cost.

What changed

  • NestJS was removed from the runtime path.
  • The backend is now edge-native with Hono.
  • Shared contracts are handled through Zod and oRPC.
  • PostgreSQL stays external, while the API runtime moves to Workers.

Why it matters

This architecture keeps the public portfolio and the studio/admin surface available on a free-tier friendly platform, while keeping the operational burden low.

Practical outcome

The result is a simpler deployment shape: Pages for the client, Workers for the API, and Neon for PostgreSQL.