How klebervirgilio/react-crud-app-with-golang works
Main high-level components
• Front-end SPA: React application (pkg/http/web/app)
• API Server: Go HTTP server (cmd/main.go + pkg/http)
• Service Layer: Business logic (pkg/kudo/service.go)
• Domain & Repository Interface: Core models and interfaces (pkg/core)
• Persistence Layer: MongoDB concrete repository (pkg/storage)
• Auth Provider: Okta JWT verification (pkg/http/middlewares.go)
• External API: GitHub REST API for searching repos
• Database: MongoDB (via docker-compose)
Relationships and data flows
• User’s browser → React UI →
• Calls Go API endpoints (/kudos) with Authorization header
• Calls GitHub API for search (client-direct)
• Redirects to Okta for login, receives JWT token
• Go API server →
• Middleware chain: CORS → JWT validation with Okta → JSON headers → Logging
• Router (httprouter) dispatches to handlers → Service layer → Repository interface
• Repository interface bound to MongoRepository implementation → MongoDB
• Go API server does *not* call GitHub API directly.
• MongoDB persists Kudo documents.
Architectural patterns
• Layered/Clean architecture:
• Presentation (pkg/http)
• Application/service (pkg/kudo)
• Domain (pkg/core)
• Infrastructure (pkg/storage)
• Interface-driven design: core.Repository interface decouples service from persistence.
• Middleware pipeline for cross-cutting concerns (auth, CORS, logging, JSON API).
• Micro-frontend-style SPA: React app isolated under /pkg/http/web/app.
Technologies/frameworks
• Front-end: React (create-react-app), Material-UI, react-router, Okta React SDK
• Back-end: Go, julienschmidt/httprouter, okta-jwt-verifier, rs/cors
• Persistence: MongoDB (globalsign/mgo driver), Docker Compose
• Build & deploy: Makefile, Procfile, Docker Compose