How zocketzero/poker-game-backend works
Poker Backend is a real-time Texas Hold’em server. Clients register or log in over REST, then authenticate a WebSocket session to browse/create tables, join seats, and play hands; game updates return over the socket. The lobby coordinates table actors, which wrap poker_engine and deliver private cards and public events. MongoDB persists users, chip balances, and hand histories. The README documents tournaments and full NLHE support; sampled excerpts show key session, lobby, table, and persistence paths, but not every route or game operation.
Main entry points: handler.rs Socket sessions · auth_handlers.rs Register and login · user_repository.rs User repository · table_actor.rs Game table actor
Components 19
HTTP and sessions
- HTTP server
src/main.rs - Auth routes
src/routes/auth_route.rs - WebSocket route
src/routes/ws_route.rs - Socket sessions
src/ws/handler.rs - Socket protocol
src/game/messages.rs
Identity
- Register and login
src/auth/auth_handlers.rs - Auth request types
src/auth/auth_dtos.rs - Username rules
src/auth/regex.rs - JWT tokens
src/auth/jwt_manager.rs - Configuration
src/config.rs
Lobby and gameplay
- Table lobby
src/game/lobby.rs - Game table actor
src/game/table_actor.rs - poker_engine
Persistence
- User repository
src/repositories/user_repository.rs - User and hand models
src/db/models.rs - Collection names
src/db/collections.rs - Mongo connection
src/db/connection.rs
Other components
- Players
- MongoDB
Connections 24
- Players → HTTP server: HTTP requests
README.md - HTTP server → Auth routes: serves REST
README.md - HTTP server → WebSocket route: serves socket
README.md - Auth routes → Register and login: routes auth
src/routes/auth_route.rs - Players → Register and login: registers or logs in
README.md - Register and login → Auth request types: accepts
src/auth/auth_handlers.rs - Register and login → Username rules: validates names
src/auth/auth_handlers.rs - Register and login → User repository: creates or finds users
src/auth/auth_handlers.rs - Register and login → JWT tokens: creates token
src/auth/auth_handlers.rs - WebSocket route → Socket sessions: upgrades connection
src/routes/ws_route.rs - Players → Socket sessions: connects with token
README.md - Socket sessions → JWT tokens: validates token
src/ws/handler.rs - Socket sessions → Socket protocol: parses and sends
src/ws/handler.rs - Socket sessions → Table lobby: dispatches table requests
src/ws/handler.rs - Socket sessions → User repository: checks and updates chips
src/ws/handler.rs - Table lobby → Game table actor: manages tables
src/game/lobby.rs - Game table actor → poker_engine: runs poker game
- Game table actor → Socket protocol: emits game messages
src/game/table_actor.rs - Game table actor → User repository: saves hand history
src/game/table_actor.rs - Game table actor → User and hand models: builds history records
src/game/table_actor.rs - User repository → User and hand models: reads and writes
src/repositories/user_repository.rs - User repository → Collection names: uses collection name
src/repositories/user_repository.rs - User repository → MongoDB: persists documents
src/repositories/user_repository.rs - Mongo connection → MongoDB: connects