The Action Network

Our engineering team operates on weekly Sprints. Each cycle begins with a meeting to discuss time estimates for features every Tuesday. Engineers typically work very closely with the product owner and any other interested parties to spec a feature, then work on the feature. We use Pull Requests on GitHub to conduct code reviews. All engineers are also empowered to push code to production, which we often do multiple times a day. Since our team builds applications for both web and mobile, we have CI/CD setup that allows us to deploy our Backend code and web code to be deployed as many times a day as needed. For our mobile apps we stick to a 2 week release cycle and try to get new features and bug fixes out to users every 2 weeks.

Sports data has a fair number of technical challenges: - Diverse data model (Many different types of sports with their own unique data structures) - Real time (1000's of events occurring every second) - Spiky Traffic patterns (We frequently see busy sporting days where users will hit our APIs at 5k - 6k requests per second!) - Event driven user needs (When certain conditions occur for an event a massive number of users would like to be alerted immediately) - Predictive analytics for our projecting event outcomes as the event progresses