Introduction to Microservices

Game Server Services provides a number of microservices to implement in-game features. The microservices described in this section will be implemented in combination according to the specifications of your game.

This section focuses on what each GS2 microservice can do to help game developers plan their games.

How to combine microservices

GS2 microservices each have independent responsibilities, but cooperate via transaction actions. For example, the following kind of cooperation safely realizes complex game logic.

graph LR
  Player[Player] -- Payment --> Platform[AppStore/GooglePlay]
  Showcase[GS2-Showcase] -- Product List --> Player
  Player -- Purchase (with Receipt) --> Showcase
  Showcase -- Issue Transaction --> Distributor[GS2-Distributor]
  Distributor -- Consume Action (Receipt Verification) --> Money
  Distributor -- Acquire Action (Item Acquisition) --> Inventory

Each service exposes transaction actions called “verify actions”, “consume actions”, and “acquire actions”. By chaining these together via GS2-Distributor, processing that spans multiple services can be executed atomically.

How to proceed with learning

If this is your first time using GS2, we recommend starting by understanding GS2-Account. The concept of an anonymous account is the prerequisite for all GS2 services.

Next, by reading through the pages of the feature categories your game needs in order, you can grasp how to choose services for the overall system design of your game.