How syedahmedullah14/blogging-app-like-medium works
Project type and purpose
• This is a full-stack blogging application (Medium-style) built as a monorepo.
• Frontend: React + Vite + Tailwind (deployed to Vercel)
• Backend: Cloudflare Workers (TypeScript) using Prisma ORM + PostgreSQL (deployed via Wrangler)
• Common: Shared TypeScript utilities/types across frontend & backend
File structure
• Root: README.md points to live demo, tech stack, features
• backend/
• src/index.ts – Worker entrypoint
• src/route/blog.ts, user.ts – HTTP handlers
• prisma/ – schema.prisma + migrations (PostgreSQL schema + connection pooling)
• wrangler.toml – Cloudflare Workers config
• package.json, tsconfig.json – build & typings
• common/
• src/index.ts – shared types or helpers
• dist/ – compiled output for npm linkage
• frontend/
• src/ – React app (App.tsx, pages, components, hooks, config.ts)
• public/index.html – SPA host
• vite.config.ts, tsconfig*, tailwind.config.js – build/tooling
• package.json – dependencies (React, Skeleton UI, Zod client‐side)
README for additional insights
• Authentication via JWT
• Zod for validation/type inference
• Skeleton loading in UI for better UX
• Connection pooling in Prisma
a. Main components
1. Client (Browser/SPA)
2. CDN / Vercel (serving static assets)
3. Cloudflare Workers (serverless API)
4. Prisma ORM (hosted within Workers)
5. PostgreSQL Database
6. Shared “common” library (types/validation logic)
7. External services: Cloudflare KV or Secrets (for JWT_SECRET, DB URL)
b. Relationships & data flow
• User → Browser → SPA (React)
• SPA makes HTTP calls to Cloudflare Workers endpoints (/api/user, /api/blog)
• Worker executes route logic → uses shared common code (Zod schemas, types) → Prisma client
• Prisma client communicates with PostgreSQL → returns data
• Worker signs/verifies JWT (using secrets stored in Cloudflare environment)
• JSON response back to SPA → UI renders with Skeleton loaders
c. Architectural patterns & principles
• Monorepo with three packages (frontend, backend, common)
• Serverless backend: each route is an isolated function in Workers
• Shared code: common library for DRY validation/types
• MVC-lite: route handlers (controllers) → Prisma (model) → JSON (view)
• Zero-trust/auth: JWT for session management
d. Key technologies
• React + Vite (SPA build & dev server)
• Tailwind CSS + postcss (UI styling)
• Cloudflare Workers + Wrangler (serverless deployment)
• TypeScript + Zod (static typing & runtime validation)
• Prisma ORM + PostgreSQL (data layer + migrations)
• JWT (authentication)
Final pointers
• Layer (UI, API, Data) distinctly.
• External services (Secrets, CDN) to show operational dependencies.
• Authentication flow (JWT issuance & verification).
• Monorepo structure by grouping code artifacts (folders) under each component.
• Don’t overcomplicate: break the system into as many logical components as necessary for clarity.