An interactive architecture notebook about building a private, dependable full-stack product without building a platform larger than the problem.
EverDuet is intentionally small enough to understand end to end. That makes it a useful full-stack laboratory: product behavior, database invariants, authentication, performance, queues, testing, containers, and operations all exist—but each earns its complexity.
The boundary between layers matters more than the framework inside each box.
Two server-rendered apps keep the private couple experience separate from administrative curation.
A single permission-heavy application shell
Throughput is modest, but privacy, concurrency, migrations, and recovery still deserve correct boundaries.
The public API and queue are useful seams to study, not excuses to invent clients or background work.
Prompt flows should feel immediate and safe. Performance work follows user-visible waits and protects private state.
Automation should increase confidence without creating a platform that needs its own operator.
IMPORTANT
This site describes the current repository, not an idealized reference architecture. When a choice is educational but not yet product-critical—such as BullMQ—it says so directly.
Continue to the system map, or jump to the guided code tour if you learn best from source.