How aksevinch/soa-1 works
This repository is an architecture-design exercise for a digital marketplace, with one deliberately minimal runtime service. The implemented workflow is a GET /health request returning JSON with HTTP 200; it has no marketplace business logic. The README documents broader planned domains and integrations, but these are not implemented in the sampled source. Relationships for those planned components are shown only where the README explicitly states them.
Main entry points: 02-container.md API Gateway · main.go Catalog service
Components 15
Implemented runtime
- Catalog service
services/catalog-service/main.go
Planned marketplace
- Web Portal
docs/c4/02-container.md - API Gateway
docs/c4/02-container.md - Identity Service
docs/c4/02-container.md - Identity DB
docs/c4/02-container.md - Catalog domain
docs/c4/02-container.md - Catalog DB
docs/c4/02-container.md
Other components
- HTTP client
- Buyer
- Seller
- Moderator
- Payment gateway
- Delivery API
- Notification providers
- Identity provider
Connections 14
- HTTP client → Catalog service: requests health
services/catalog-service/main.go - Catalog service → HTTP client: returns 200 JSON
services/catalog-service/main.go - Buyer → Web Portal: uses portal
README.md - Seller → Web Portal: uses portal
README.md - Moderator → API Gateway: moderates
README.md - Web Portal → API Gateway: sends requests
README.md - API Gateway → Identity Service: routes requests
README.md - API Gateway → Catalog domain: routes requests
README.md - Identity Service → Identity DB: owns data
README.md - Catalog domain → Catalog DB: owns data
README.md - API Gateway → Payment gateway: handles payments
README.md - API Gateway → Delivery API: requests delivery
README.md - API Gateway → Notification providers: sends notices
README.md - Identity Service → Identity provider: delegates login
README.md