Containers
The fifteen deployable units, their ports, and the calls between them (C4 level 2).
Two boundaries. store-core runs once per environment: six containers and one Postgres. store-pod runs once per pod: nine containers, one Postgres and one object store. Every pod is a complete, isolated copy; nothing in a pod is shared with another pod. The shapes follow the legend.
Diagram C2
What the edges mean:
- console-ui → gateway. The console is served by the gateway's catch-all route and calls the platform APIs on the same origin under
/tenancy/**,/billing/**,/pod-registry/**and/uaa/**. It holds no token; the gateway's session does. - gateway → tenancy, billing, pod-registry, uaa.
GatewayRouteLocatorImplstrips the prefix and relays the signed-in user's token (tokenRelay()). The/uaa/**route alone keeps its prefix and addsX-Forwarded-Prefix: /uaa. - gateway → spg.
PodClientbuilds one route per pod at runtime:/spg/**withstore=andpod=query parameters,StripPrefix=1,TokenRelay. This is how a merchant edits a product that lives in any pod through one origin. See Gateway routing. - spg → pod services and landing-ui. The Caddyfile path-routes
/content*,/merchant*,/inventory*,/catalog*,/checkout*,/cua*,/payment*; everything else goes tolanding-uiafterdomain_lookuphas injected the store headers. See store-pod and Edge and custom domains. - landing-ui → spg (server-side). The storefront's server renders read merchant, content, catalog, checkout and inventory through the pod's own spg (
INTERNAL_SPG), so a server-side read and a browser-side call take the same route. - pod services → uaa. Every pod service is a JWT resource server that accepts tokens from
uaa(staff) andcua(shoppers), and authenticates to its peers with aclient_credentialsclient againstuaa. See Authentication. - catalog → billing.
catalog-coreguards product writes withStoreEntitlementsfrombilling-external-api. It is the one call from a pod back intostore-core. - payment → Stripe, billing → Stripe. Store payments and platform subscriptions; each receives Stripe's webhooks on its own public endpoint.
The fifteen containers
| Container | Layer | Port | Runtime | Owns | Fronted by |
|---|---|---|---|---|---|
store-core-gateway | store-core | 8000 | Spring Cloud Gateway (WebFlux) | The browser session, the OAuth2 client login against uaa, token relay, the per-pod route table | itself (gateway.com) |
uaa | store-core | 8001 | Spring Boot, embeds Angular uaa-fe | Staff and merchant identity: OAuth2 authorization server and OIDC provider, users, roles, clients, brokered login, its admin app | store-core-gateway (/uaa/**); its own host uaa.gateway.com |
console-ui | store-core | 8011 | Angular 20 SSR | The merchant and platform-admin console | store-core-gateway (catch-all) |
tenancy | store-core | 8020 | Spring Boot | Organizations, stores, members, sign-up, the store → pod binding, store provisioning through the outbox | store-core-gateway (/tenancy/**) |
billing | store-core | 8021 | Spring Boot | Plans, per-store subscriptions, the Stripe webhook, entitlements and store quotas | store-core-gateway (/billing/**) |
pod-registry | store-core | 8022 | Spring Boot | The pod catalog: identity, endpoint, health, capacity, placement | store-core-gateway (/pod-registry/**) |
spg | store-pod | 80 / 443 | Caddy | On-demand TLS for custom domains, domain → store lookup, path routing into the pod | itself (the store's host) |
landing-ui | store-pod | 8110 | Next.js 16 / React 19 | The storefront: one app, every theme, the page cache | spg (fall-through) |
merchant | store-pod | 8120 | Spring Boot | Store configuration: languages, currency, domains, address; the routing hooks spg calls | spg (/merchant*) |
content | store-pod | 8121 | Spring Boot | Pages, posts, banners, FAQ, policies, menus, media library, site settings and appearance | spg (/content*) |
catalog | store-pod | 8122 | Spring Boot | Products, variants, options, categories, brands, product types and groups, images | spg (/catalog*) |
checkout | store-pod | 8123 | Spring Boot | Cart, orders, customers, countries | spg (/checkout*) |
cua | store-pod | 8124 | Spring Boot | Shopper identity: a headless OAuth2 authorization server, registration, social login | spg (/cua*, prefix kept) |
payment | store-pod | 8125 | Spring Boot | Payment provider configuration per store, payment execution, provider webhooks | spg (/payment*) |
inventory | store-pod | 8126 | Spring Boot | Stock, prices and reservations, keyed by sku | spg (/inventory*) |
Ports, hostnames and the fronting gateway (gateway-service-name) are recorded per service in common-config.yml. A service is reachable on its own port only inside its namespace (store-core.cvhome.lcl, store-pod-<id>.cvhome.lcl); from anywhere else it is a path on its gateway, with the prefix stripped (except /cua and /uaa).
Data
Each Spring Boot service owns one Postgres schema, named after the application (pod_registry, content, payment, ...), and ships its own DDL as a schema.sql. Foreign keys never cross a schema. store-core shares one Postgres; each pod has its own. content, merchant and payment configure an S3 client for files (MinIO locally; S3 behind CloudFront on AWS), and spg keeps its certificates in an S3 bucket.
Shared libraries
store-commons/ is libraries only; nothing in it is deployed. Every service inherits its cross-cutting behavior by depending on these modules:
| Module | What it gives a service |
|---|---|
commons | The value objects used everywhere in place of raw strings: StoreMerchantId, ManagerOrgId, PodId, LanguageCode, Pod, PodEndpoint, Theme, ... |
errors | The shared error catalog and ProblemDetail handling |
autoconfigure | Multi-issuer JWT decoding, the permission evaluator, web clients, and the shared YAML (common-config.yml, lcl-config.yml, fargate-config.yml) |
uaa-client, uaa-client-impl | A typed SDK for uaa's admin API |
sso/sso-core, sso/sso-events | The authorization-server core that uaa and cua are both built on |
secret-crypto/* | Encryption of stored secrets (payment keys, social-login credentials): local AES or AWS KMS, with a caching decorator |
ecs-commons/* | Cloud Map service discovery and ECS task metadata for Fargate; inert locally |
test-support | Testcontainers, test JWT signing and the integration-test annotations; never on a production classpath |
ui-kit | The Angular component kit console-ui and uaa-fe share |
A second module is also called store-commons: store-pod/commons/store-commons is the pod-scoped shared domain. Refer to either by its Gradle path.
Images
Container images are named <layer>/<service>: store-core/uaa, store-core/console-ui, store-pod/catalog, store-pod/spg, and so on. Nothing deploys from the application repository's CI; images build in CodeBuild and Terraform applies them. See Deployment: AWS and Deployment: local.
Source of truth: cvhome store-commons/autoconfigure/src/main/resources/common-config.yml, store-pod/spg/Caddyfile, store-core/gateway/gateway-service/src/main/java/com/asrevo/cvhome/gateway/config/GatewayRouteLocatorImpl.java, store-core/gateway/gateway-service/src/main/java/com/asrevo/cvhome/gateway/client/PodClient.java, .claude/skills/project-structure/SKILL.md and references/{store-core,store-pod,shared-libraries,database-schemas,service-to-service}.md, store-pod/catalog/catalog-core (StoreEntitlements), store-pod/landing-ui/libs/services/src/store-context-ssr-utils.ts.