Pastebin Clone

Problem

I wanted a small, real backend exercise that still forced useful decisions: identifiers, expiry thinking, storage shape, and a readable HTTP surface.

Approach

Built a paste service in Go with explicit handlers and a narrow domain model. The goal was clarity over framework magic — request in, validated paste out.

Architecture

• HTTP handlers own transport concerns only
• Domain types stay free of framework types where practical
• Persistence behind a small interface so the API stays testable

Outcome

A compact backend project that demonstrates how I like services to feel: boring in the best way, explicit about ownership, and easy to extend.