How cp-rektmart/pic-me-pls-backend works
Project type and purpose
• This is a Golang monolithic backend service (“Pic-me-pls-backend”) providing REST+WebSocket APIs for a photo‑sharing/booking platform.
• Key features: authentication (JWT), chat (real‑time via WebSocket), media upload & object storage, user/photographer management, package & quotation workflows, reviews, reporting, Stripe‑based payments.
• Deployed locally via Docker Compose (Postgres, Redis, optional MinIO), with code generation for DTOs & Swagger docs.
File structure
• cmd/main.go: application entry point
• internal/…: core business logic
• server/ (register routes & docs)
• middlewares/ (auth, logging)
• services/ (one subfolder per domain: auth, user, category, media, message/chat, quotation, packages, review, report, stripe, etc.)
• database/store.go: persistence interface
• model + dto: domain models vs external data contracts
• jwt, validator, config, utils (pagination, etc.)
• pkg/…: shared infrastructure abstractions
• postgres, redis, storage, httpclient, logger, apperror, requestlogger
• doc/: Swagger/OpenAPI specs
• Dockerfile, docker-compose.yml, .env.docker: containerized infra
README for additional insights
• Confirms Docker Compose for Postgres/Redis
• “air” for hot‑reload, Makefile targets
• Pre‑commit, linting & codegen steps
Relationships & interactions
• Client → HTTP/WS → API Layer → Service → Persistence/Cache/Storage/External
• Service implementations depend on store interfaces (dependency inversion)
• Media & object flows go to object storage
• Real‑time chat uses WebSocket endpoint + Redis/pub‑sub or DB back‑end
• Stripe API calls for payment flows
Architectural patterns & principles
• Clean/Hexagonal architecture: clear separation between
• Adapters (HTTP, WebSocket)
• Use‑cases (services)
• Ports (store interfaces)
• Infrastructure (Postgres, Redis, Storage, Stripe client)
• DTOs shield internal models from API contracts
• Middlewares handle cross‑cutting concerns (auth, logging)
Detail
• Break out each major service folder rather than lumping “business logic” together
• Middleware pipeline before reaching route handlers
• Config loader & JWT signer as foundational components