How ergali-zhansugurov/my_manga works
This appears to be a manga-catalog service with HTTP resources for titles, categories, users, and publishers, backed by PostgreSQL and a cache-broker integration. The intended request path is client → HTTP server → resource handler → store interface → PostgreSQL repository → database. The README provides no product detail, and sampled code does not show category/title handlers, the aggregate broker implementation, or publisher mounting; those links are omitted where wiring is uncertain.
Main entry points: cache_broker.go Cache broker · server.go HTTP server · store (2).go Store interfaces · models Domain models
Components 14
HTTP API
- HTTP server
internal/http/server.go - Category resource
internal/http/categories.go - Title resource
internal/http/title.go - User resource
internal/http/users.go - Publisher resource
internal/http/publishers.go
Data layer
- Store interfaces
internal/store/store (2).go - Postgres repositories
internal/store/postgres - Domain models
internal/models
Cache messaging
- LRU cache
internal/models/cache.go - Cache broker
internal/massage_broker/broker/cache_broker.go
Other components
- API client
- PostgreSQL
- Kafka
- Application setup
internal/app/main.go
Connections 24
- API client → HTTP server: sends requests
- HTTP server → Category resource: mounts routes
- HTTP server → Title resource: mounts routes
- HTTP server → User resource: mounts routes
- Category resource → Store interfaces: calls repositories
- Title resource → Store interfaces: calls repositories
- User resource → Store interfaces: calls repositories
- Publisher resource → Store interfaces: calls repositories
- Store interfaces → Postgres repositories: implemented by
- Postgres repositories → PostgreSQL: queries
- Postgres repositories → Domain models: maps records
- Category resource → Domain models: uses types
- Title resource → Domain models: uses types
- User resource → Domain models: uses types
- Publisher resource → Domain models: uses types
- Application setup → HTTP server: configures
- Application setup → Postgres repositories: connects
- Application setup → Cache broker: connects
- Cache broker → Kafka: publishes and consumes
- Cache broker → LRU cache: applies commands
- Category resource → Cache broker: invalidates cache
- Title resource → Cache broker: invalidates cache
- User resource → Cache broker: invalidates cache
- Publisher resource → Cache broker: invalidates cache