Startups Using Play Framework in Boston
Via their job posts and information submitted by startups themselves, these are the Boston Play Framework startups we've found.
Interested in other technologies? Browse or search all of the built-in-boston tech stacks we've curated.
Predictive analytics for healthcare data, targeting preventable admissions, member retention, and risk-based reimbursement eligibility.
Tech Stack Highlights
Machine Learning – We build models on our Spark platform using MLlib as well as in custom Python environments where we use many of the popular Python-based machine learning libraries. We’ve invested the most in using the Pytorch library, which we use for our deep learning models.
Spark & Scala – We use a Scala-based data pipeline hosted on Spark to ingest customer data and prepare it for use in our models.
Zeppelin & Jupyter – We work with data using Zeppelin notebooks for Spark and Jupyter in our Python environments.
Automation & Infrastructure – We use CircleCI to build and deploy both our services and infrastructure. We use AWS Lambda to automate infrastructure tasks and create custom notifications and alerts to simplify our internal workflows.
AWS – We host our infrastructure on AWS. We’ve built an independently audited platform that supports working with protected health information.
Tech Stack Highlights
MySQL – We use MySQL for a principal data store, mainly because we inherited that from the MVP, but we don’t have many complaints about it. We’re starting to use ElasticSearch as a data warehouse for OLAP and to optimize heavy queries. It’s REST-first design works nicely for us, and the speed is unbeatable.
Play Framework – We use Play / Scala for the heart of our platform: the API. We don’t serve any pages out of play, but it works nicely to provide a REST API. Scala takes a bit of learning, but it provides OO hooks to ease you into functional programming.
Backbone.js – Most of our web app is based on Backbone, for better or worse. It was the right decision four years ago when we started using it, and holds up fairly well. It’s stable, but being so event driven can make it hard to reason about.
React.js – Newer parts of our app are being built in React, which we’re very optimistic about. We’re hoping to take advantage of code re-use by repackaging with React Native for mobile app use.
Amazon Web Services – We run everything on AWS, which makes life easy, if sometimes expensive. We’re trying to avoid vendor lock-in by steering clear of their branded products as much as makes sense, and instead using plain old computer resources. Jenkins runs our continuous integration, which is a hugely important part of our process. As an agile shop we want to de-dramatize releases; CI makes this process so easy that it’s possible to release without worrying.