Go Backend Engineering Portfolio
Four backend case studies that separate current implementation from target architecture, backed by an interactive demo and a real Go repository.
Finish HTTP/service boundaries: handler validation, service-layer results, errors.Is error mapping and handler/service/domain tests.
Acceptance evidence (planned):
An order HTTP service demonstrating validation-driven boundaries today and a full lifecycle core — state machines, idempotency, optimistic concurrency and a transactional outbox — as the target.
Runtime: Local development only. Demo data: mocked (MSW)
Four backend case studies. Order is in development; Auth, Notification and the URL shortener are at the specification stage with real specifications.
An order HTTP service demonstrating validation-driven boundaries today and a full lifecycle core — state machines, idempotency, optimistic concurrency and a transactional outbox — as the target.
Focus: State machines, transactions, idempotency, optimistic concurrency, transactional outbox.
Current milestone: order-http-service
A credentials-and-sessions service for the demo environment: Argon2id credential storage, short-lived access tokens, opaque rotating refresh credentials and reuse detection.
Focus: Session lifecycle, rotation and replay detection, RBAC, rate limiting.
An event-driven delivery service: durable inbox, at-least-once consumption, bounded delivery workers and retry with backoff — designed around duplicates, poison messages and recovery.
Focus: At-least-once processing, durable jobs, retry/DLQ semantics, bounded workers.
A redirect service engineered around its hot path: PostgreSQL storage, Redis cache-aside with bounded fallback, per-instance singleflight and reproducible latency benchmarks.
Focus: Redis cache-aside, singleflight, hot path, bounded analytics.
One repository, one deployment: a statically generated portfolio layer and the interactive demo SPA under /demo/. Four independently owned Go services are the target; today the order service runs locally and the demo is mocked.
Transport parsing never reaches business logic; services never read each other’s storage. Integration happens through APIs and explicit contracts.
Current, target and measured are different claims with different evidence. Planned infrastructure is never rendered as deployed.
Idempotency, optimistic concurrency, at-least-once delivery and cache-staleness bounds are first-class design content, not afterthoughts.
Mirrors the backend repository roadmap. States describe the sequence, not percentages.
Finish HTTP/service boundaries: handler validation, service-layer results, errors.Is error mapping and handler/service/domain tests.
Services: order
Agree OpenAPI/DTOs, add repository/PostgreSQL/migrations and durable create/read flows.
Services: order
Order/payment state matrix, cancellation/refund, versioning, idempotency, history and concurrency tests.
Services: order
Credentials, sessions, refresh rotation/reuse detection, RBAC, cookies/CORS/CSRF and real browser flows against the demo frontend.
Services: auth
Transactional outbox/event contract, inbox/jobs, delivery workers, retries and recovery.
Services: order, notification
Database/redirect hot path, Redis fallback, per-instance singleflight, reproducible measurements and bounded analytics.
Services: shortener
Runbook, observability, backup/restore, integration CI and reproducible public evidence.
Services: order, auth, notification, shortener