Architecture¶

This section turns the canonical domain model into the architecture required by Part I §4 of the project strategy.

The services are deployed independently from the start, as recorded in ADR-007, which supersedes the earlier modular-monolith decision (ADR-002). The microservice view below is therefore the deployment topology, not just a target decomposition.

Part I architecture¶

1. Microservices decomposition: service boundaries, ownership, and data ownership.
2. API design: public gateway contract and internal service APIs.
3. Key flows: anonymous scan, personalized scan and add-to-Fridge sequences.
4. Technology stack: languages, frameworks, infrastructure and repository layout.

Later pages should build on these service names and boundaries rather than inventing new ones.