How servicesys/gonotificationservice works
(minimal) file structure
• Top‐level only has LICENSE and README.md, implying either:
• We have a single‐module Go service (e.g. a “cmd/” folder with main.go, plus “internal/” or “pkg/” folders for business logic).
• Configuration (YAML/JSON/TOML), Dockerfile, deployment manifests, tests, etc., will be side‐by‐side or under dedicated directories.
• We’ll assume a conventional Go layout:
• cmd/notification-service/main.go
• internal/api/ (HTTP handlers, request validation)
• internal/enqueue/ (queue producers)
• internal/worker/ (queue consumers)
• internal/provider/ (APNS, FCM adapters)
• config/, deployments/, scripts/, tests/
README for additional insights
• References point to scalable, high‐throughput designs: external queueing, retry, persistence, metrics.
• No explicit tech stack beyond Go, so we infer common components (Redis/Kafka/RabbitMQ for queue, PostgreSQL/Mongo for persistence, Prometheus/Grafana for monitoring, Kubernetes for deployment).