- Postgres: every table has a uuid `id` (gen_random_uuid()); the event store keeps its relay order in `seq`, and the lookup tables their uniqueness in constraints of their own. - MongoDB: `_id` is Mongo's ObjectId; `id` is the domain id (the same uuid as the aggregate's stream in Postgres), unique, and every query goes by it. Production starts from empty databases. - Web: linking tickets and hanging one from a parent are picked from a searchable select (links across projects, parents within the project) instead of typing a key; every checkbox is @pi/ui's pi-checkbox. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
api-tracker-infrastructure
Adaptadores de salida del tracker.
- Import:
@task-stream/api/tracker/infrastructure - Capa:
infrastructure· Tags:scope:api-tracker,type:infrastructure
Contenido
postgres/: lookups de escritura (project_keys,issue_sequences,release_names),ReleaseIssuesRepositoryyTrackerStreamsRepository(consultan el event store: tickets y releases de un proyecto, comentarios y enlaces de un ticket).mongo/: esquemas del read model (incluida la línea temporalissue_timeline), repositoriosFind*yUpsertMaterialized*(upsert idempotente por versión) yStatusCategoryBackfill(al arrancar, rellena la categoría del estado en los tickets proyectados antes de existir).realtime/:RedisChangeFeed(canales de Redis pub/sub por proyecto, ticket y usuario).identity/:IdentityUserDirectory, capa anticorrupción hacia el contexto de identidad.
Comandos
npx nx lint api-tracker-infrastructure
npx nx test api-tracker-infrastructure # Jest
Reglas de dependencia entre capas: Arquitectura.