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.
Zsolt Sz. Sztupák is a senior software engineer on the platform engineering team at Gamesys, where he helps the company automate its processes. Zsolt started his professional career as an infrastructure engineer who spent most of his days laying CAT-6 cables. While he eventually ventured further into more development-oriented positions, he always remained aware that development doesn’t actually end when you finish coding. He enjoys working on security architecture while looking into new technologies like Kubernetes. Zsolt has given a number of talks on the development stack and DevOps in general.
©2017, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org