AngeloR

Datadog was used as an agent for monitoring and as for the statsd daemon included. This way we are able to have automated system stats and include whatever other metrics we want to track. Datadog

We use ElasticBeanstalk to manage the applications/deployment/scaling functionality over top of EC2.

There are a few smaller ec2 instances that are customized for the multiplayer system. Amazon EC2

We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications. CircleCI

Socket.io is used as our current multiplayer engine. The existing engine is very simplistic and only utilizes the websocket+http fallback transports and serves as a generic world/zone/screen grouping mechanism for displaying users to each other. Socket.IO

We are using RDS for managing PostgreSQL and legacy MSSQL databases.

Unfortunately while RDS works great for managing the PostgreSQL systems, MSSQL is very much a second class citizen and they don't offer very much capability. Infact, in order to upgrade instance storage for MSSQL we actually have to spin up a new cluster and migrate the data over. Amazon RDS

CC handler for our membership system. It was an easy choice for how quickly we were able to implement it, as well as the disputed payment process. Stripe

This is a legacy system requirement. We have some portions of our website written in PHP. Normally this wouldn't be an issue but at the time they decided to use PHP+Windows they were also trying to use MSSQL databases (All the microsoft influence was due to some azure credits the company received early on). The particular driver they ended up picking forced them into using the mssql_* functions instead of PDO. This meant that the majority of the site used these rather outdated calls and replacing them was a rather large endeavour. So while we migrate some of the PHP backend away to various node.js api systems we are simply sustaining the existing PHP portions. Microsoft IIS

We use ElasticSearch for

• Session Logs
• Analytics
• Leaderboards

We originally self managed the ElasticSearch clusters, but due to our small ops team size we opt to move things to managed AWS services where possible.

The managed servers, however, do not allow us to manage our own backups and a restore actually requires us to open a support ticket with them. We ended up setting up our own nightly backup since we do per day indexes for the logs/analytics. Elasticsearch

Currently serves as the location that our QA team builds various automated testing jobs.

At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines. Jenkins

S3 is where we upload various assets for the game/website/education content. Amazon S3