Overview

The Product Catalog System is the system of record for products at Acme Inc. It accepts commands to create, update and delete products, persists them in the Product DatabaseProduct DatabaseContainer•v1.0.0PostgreSQL database that is the system of record for all product data.MapView docs, and emits domain events whenever product data changes so downstream systems — like the Search SystemSearch SystemSystem•v1.0.0Internal system that keeps product data searchable. Consumes product change events from the Product Catalog System, main...Ownersearch-platformMapView docs — can react.

Context Diagram

How this system relates to the other systems around it.

Resource Diagram

The services, data stores and messages that make up this system.

What’s inside

Component	Type	Responsibility
Product APIProduct APIService•v1.0.0The public-facing API for the product catalog. Handles commands to create, update and delete products, serves product re...Subscribescreate-product, update-product +2APIsOpenAPIOwnerproduct-platformMapRepoView docs	Service	Public-facing API. Handles create/update/delete commands and product reads.
Product WorkerProduct WorkerService•v1.0.0Background worker that handles long-running and asynchronous catalog work off the request path, such as enrichment, imag...Ownerproduct-platformMapRepoView docs	Service	Processes long-running and asynchronous catalog work off the request path.
Product Search PublisherProduct Search PublisherService•v1.0.0Reads product changes from the product database (outbox) and reliably publishes product-created, product-updated and pro...Publishesproduct-created, product-updated +1Ownerproduct-platformMapRepoView docs	Service	Publishes product change events for the Search System to consume.
Product DatabaseProduct DatabaseContainer•v1.0.0PostgreSQL database that is the system of record for all product data.MapView docs	Data store	PostgreSQL system of record for all product data.

Messages this system publishes

When product data changes, the system emits these events:

• Product CreatedProduct CreatedEvent•v1.0.0Published when a new product has been added to the catalog. Ownerproduct-platformSchemaMapView docs — a new product has been added to the catalog.
• Product UpdatedProduct UpdatedEvent•v1.0.0Published when an existing product's data has changed. Ownerproduct-platformSchemaMapView docs — an existing product’s data has changed.
• Product DeletedProduct DeletedEvent•v1.0.0Published when a product has been removed from the catalog. Ownerproduct-platformSchemaMapView docs — a product has been removed from the catalog.
• ADR-001: Publish product events via a transactional outboxADR-001: Publish product events via a transactional outboxDecision Record•v1.0.0Product change events are written to an outbox table in the same transaction as the change, then relayed to the broker, ...Ownerproduct-platformView docs — a product has been removed from the catalog.

Architecture decisions

The key decisions that shaped this system. Search, filter by status, or sort by clicking a column.

Architecture Decision Records (3)

Decisions that apply to this Product Catalog System. Search, filter by status, or sort by clicking a column.

Accepted (3)

Name↕	Status↕	Date▼	Summary
ADR-003: Offload long-running catalog work to a dedicated worker	Accepted	Feb 18, 2026	Slow and asynchronous catalog tasks (enrichment, image processing, bulk imports) run in a separate Product Worker so the Product API stays fast and predictable.
ADR-002: Use PostgreSQL as the product system of record	Accepted	Feb 12, 2026	Product data is stored in a single PostgreSQL database that acts as the authoritative system of record, with derived stores (like the search index) rebuilt from it.
ADR-001: Publish product events via a transactional outbox	Accepted	Feb 10, 2026	Product change events are written to an outbox table in the same transaction as the change, then relayed to the broker, so an event is never lost or published for a rolled-back change.