How karansinghgit/feems works
Project Type and Purpose
• This is a full-stack billing management application (“feeMS”) consisting of:
– A Go backend service using Encore to expose RESTful APIs and provision infrastructure
– Temporal workflows to orchestrate durable bill state and business logic
– A Postgres database for persistent storage of bills and line items
– A React/TypeScript frontend for user interaction
File Structure
• Top level
– .gitignore, README.md, go.mod/go.sum, encore.app (Encore configuration)
– scripts/ (startup + test helper scripts)
• services/fees/
– service.go (Encore API endpoints)
– workflow.go (Temporal workflow definition with signal/query handlers)
– activities.go (Temporal activities performing DB side effects)
– types.go (shared request/response/workflow payloads)
– migrations/ (Postgres schema versioned SQL files)
– *_test.go (integration and workflow replay tests)
• frontend/
– package.json/tsconfig.json, public/ (static HTML/manifest)
– src/ (React app entrypoints, components, API client)
Extract README Insights
• API Layer: Encore exposes REST endpoints for bill lifecycle operations
• Workflow Layer: Temporal workflows maintain per-bill state and handle signals (add item, close bill)
• Activities: Execute side-effects against Postgres (create/update bills & line items)
• Database: Postgres via Encore’s sqldb abstraction
• Frontend: Thin React app communicating with Encore API