During my time at Sky Bet, I worked within the GLS (game launch service) squad. As the team name suggests, the service was responsible for providing game launching for all gaming content across the business.

Background

The team/GLS project was born out of the necessity for multiple websites to be able to communicate with all external gaming suppliers in a common way. Without going too deep into the matter, each gaming supplier has slightly different APIs, different responses etc. As you can imagine, having to repeat this code for each website would be error-prone and be quite cumbersome. To remedy this, the GLS service provides a React component which consumers can embed into their websites which allows them. Given that this project is what's referred to as a 'p1 service' (mission critical service) we made extensive use of monitoring technologies such as Prometheus, Grafana and NewRelic to be able to monitor and respond to any incidents that occur within our project scope.

During my time in this team, I worked within GLS on things such as

• Promotion tracking within game sessions
• Time based scaling POC within AWS crucial infrastructure
• Maintenance of the service
• Improvement of Dev/Deploy pipelines
• Run demos for stakeholders on what we’re building
• Discussing the wider tech strategy and making judgement calls on how the decisions we make affect other teams and areas of the business

Outside of GLS I also had involvement in:

• RCS (reality check service). Reality check is a safer gambling tool which is a mandatory safer gambling tool that all UKI based betting companies have to include as part of their safer gambling tooling. Again this was a 'p1 service' which was responsible for reminding users to take a break from betting. Under the hood, it utiizes Redis for it's caching layer, DynamoDB for it's persistence layer, AWS Lambda + API gateway as it's compute layer.