Knowledge is power. In order to effectively build software that empowers our customers to be more successful, we have to know everything about how they interact with our features and how they’re able to achieve their specific goals.
In our last blogpost, we talked about how we completely re-imagined tournament creation. Incidentally, the results of transforming a legacy user interface which forced tournament organizers to create stages (single elimination, double elimination, round robin, swiss), adding participants (teams, free agents), and even the tournament rules upfront to a 2-step process where tournament organizers could select a game, type in a tournament name and select a start date was mind-blowing.
On average, the original design for tournament creation took about 10 minutes because it required organizers to fill in everything upfront. Now, you can create your tournament within seconds and make edits with your admins in real-time.
At Battlefy, we’re extremely data-driven. We wanted to share with the technology community how we’re able to get precise data on our users to make better decisions on product strategy:
With this automated pipeline, we’re now able to get the following:
If we catch any trends on the usage of specific features, we take a look at how and why that growth is happening, we ideate on how we can increase that growth, and then ship it.
As you may already know, our original platform was solely built with NodeJS and MongoDB. As we continue to be a polyglot engineering culture, we do our absolute best to utilize technologies best suited for the job. That being said, getting sales data from MongoDB felt like an uphill battle; however, spending a day building an ETL process to transform Mongo collections into 3rd normal form in MySQL seemed like the most scalable solution and wouldn’t require too much engineering effort for support (reporting is super easy to setup on Periscope ). So far, our business intelligence and sales team have been really happy with the results because they only need to use Periscope to get the reports they need and engineering hasn’t had to make any changes since it is an automated Jenkins job that happens at night.
Engineering at Battlefy works extremely hard to provide a scalable platform to power all of eSports. Dealing with legacy systems and technology becomes easier as your team starts to practice strangulation techniques, indoctrinate polyglot engineering, as well as, move towards microservice architecture.
If you have any questions (If you’re an engineer, I’m sure you’ll have questions about our pipeline), feel free to tweet us @Battlefy or comment below!
