Service Topology

Topology diagram

The diagram below shows the real service graph and the two distinct request paths: proxied data calls (browser → studio server → BFF) and the direct chat stream (browser → ai-assist).

Reading the graph

• studio — :3000. The rep console plus a server proxy layer (app/api/*). Every browser data call goes through a Next.js route that injects server-derived session identity the browser can't forge.
• ai-assist — :8080. An Express service running the LLM streamText loop. It calls the BFF through bffQuery, and reads/writes memory in Redis and MongoDB.
• BFF gateway — :4000. An Apollo Gateway that federates the commercetools, ticketing and admin subgraphs. It stamps commerce-platform, project, client, role and user headers onto every subgraph request.
• auth — :4360. A plain node:http service (not federated) handling login, sessions and project selection over REST.
• Subgraphs. commercetools (:4310) wraps the real commercetools API; ticketing (:4350) and admin (:4370) are Mongo-backed.

Diagrams & screenshots

Reference images belong under public/img/ and are rendered like:

![Service topology](/img/architecture/topology.png)