sebgrz / tiny-battleship

A battleship multiplayer game made in microservices approach

tiny-battleship

tiny-battleship's Issues

[ActiveGamesProjection] add new service

With configuration and setup like:

• events receiver mechanism
• events handlers
• state

Rtm service

A service that expose websocket gateway. It's for real-time communication between both a client and backend side.
Each events desire to game state change are send to the client game for real-time entertainment.

• basic service structure
• logic for events transmission between internal services and connected clients

[GameLogic] - implementation of replay events functionality - build game state from events!

[API Gateway]

An mediator between both client and backend side. This service should expose REST endpoints for client application and then translate them for internal events for other services.

[GameLogic] - send new pending events to message bus (rabbitmq)

[GameProjection] - service that represent latest state of each games

The service receive events from the game logic service and build current state for each games.
This application expose games via grpc protocol.

• basic, working service structure
• create event handlers and add games states builder
• expose games via grpc protobuf

Dockerize all the stuff

Adding Dockerfiles to all services and then add them to the docker-compose with correct environment variables

Lerna integration