How dhij/go-next-ts_chat works
Project type and purpose
• This is a full-stack, real-time chat application.
• Frontend: Next.js + TypeScript + Tailwind CSS.
• Backend: Go microservice providing both REST endpoints (user auth/management) and WebSocket endpoints for real-time messaging.
• Database: SQL (users table via migrations).
File structure
Top-level directories
• client/ – Next.js app
– pages/ (UI routes: login, chat app)
– modules/ (AuthProvider, WebSocketProvider)
– components/ (ChatBody UI)
– constants/, styles/, public/
• server/ – Go service
– cmd/main.go (entry point)
– router/router.go (defines HTTP & WS routes)
– internal/user (user_repository, service, handler)
– internal/ws (hub.go, client.go, ws_handler.go)
– db (db.go, migrations)
– util/password.go
– Makefile, go.mod/sum
README for additional insights
• Describes “hub” architecture: a central goroutine managing rooms, channels (Register, Unregister, Broadcast).
• Sequence: client connects → ws/joinRoom → hub registers client → client.readMessage → hub.Broadcast → hub distributes → client.writeMessage → UI.