The road taken
A few years ago, Gamesys began to modernize its platform. Moving to a containerized microservice architecture was a big part of this journey. While the road taken was long and bumpy, the team was able to fulfill most of its promises. Zsolt Sztupk shares Gamesys's experience, pinpointing various design decisions that both helped and hindered the team in achieving what they wanted.
| Talk Title | The road taken |
| Speakers | Szilard Zsolt Sztupak (Gamesys) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | London, United Kingdom |
| Date | October 16-18, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Three years ago, Gamesys was still running on an old monolithic architecture to handle its gaming business. While this was manageable when the company only employed a handful of people, it wasn’t scaling well as the technical department reached hundreds of developers. Problems like late integration, communication issues between teams, and fixed-term monthly releases meant that the company couldn’t get its features and stories done in time or with the quality it desired. Gamesys planned to move to a microservice architecture to combat these problems and decided on a few technical and organizational changes early on, including: Zsolt Sztupák shares Gamesys’s experience, pinpointing various design decisions that both helped and hindered the team in achieving what they wanted.
