How iamkirillnb/avtodom works
AvtoDom looks like a URL-redirect lookup service: its configured entry point builds a PostgreSQL repository and gRPC handler, then an HTTP client asks the handler for a URL and follows the returned destination. The sampled main function calls the gRPC method directly; it does not start a gRPC server. The README documents PostgreSQL setup and migrations, but the migration SQL was not sampled, so the graph does not infer schema details.
Main entry points: main.go Service wiring · http.go Link follower · grpc.go Redirect API · db.go URL repository
Components 8
Startup and configuration
- Config loader
internal/config.go - Service wiring
cmd/main.go
Redirect lookup
- Redirect API
internal/handlers/grpc.go - URL repository
internal/repos/db.go - PostgreSQL
HTTP following
- Link follower
internal/handlers/http.go
Other components
- Application entry
- Destination site
Connections 9
- Application entry → Service wiring: starts
cmd/main.go - Service wiring → Config loader: loads config
cmd/main.go - Service wiring → URL repository: creates repository
cmd/main.go - Service wiring → Redirect API: creates API
cmd/main.go - Service wiring → Link follower: calls follower
cmd/main.go - Redirect API → URL repository: looks up URL
internal/handlers/grpc.go - URL repository → PostgreSQL: queries
internal/repos/db.go - Link follower → Redirect API: requests destination
internal/handlers/http.go - Link follower → Destination site: sends GET
internal/handlers/http.go