Problems Conclusions Future Development

During the development we noticed some issues with our tech-stack, the gameplay concept and our service development as a whole. Therfore we want to document these concerns in order to give further developering a basis.

Gameplay

• We had huge problems with the command obfuscation as we initially could not associate a game, round or player with a command. Therefore we're storing every event in an internal event store and try to perform a resolution at the end of a round, as the Game Service provided an synchronous endpoint which allows us to associate the command with a round and a player. However, this endpoint makes the whole obfuscation useless.
• We need to perform various synchronous calls

Tech-Stack

• Because we are storing every event in a relational database when it occures as an internal event store but do not use any relations, the relational database complicated the process drastically. We could'nt use strong references without an additional overhead and needed to deal with weak references and exhausting query design.
• Probably a NoSQL Database would be better in this case. Document-Oriented, Wide-Column and Key-Value came to our minds.

Service Development

• Because of the points listed above the service development felt kinda "messy" and "unclean".
• Testing is near to impossible without a realistic database dump
• The service itself is not resilient and needs much more error- and edge-case-handling.
• Probably most of the points will