Startups Using CloudFormation in Boston
Via their job posts and information submitted by startups themselves, these are the Boston CloudFormation 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.
Tech Stack Highlights
Scala and Spark – Used for our batch processing backend and for machine learning pipelines. This stack provides us with the flexibility in data science approaches as we tackle new use cases and customers as well as the ease of integration in production.
Angular2, NodeJS, and Play! Framework – Our user-facing stack for both our frontend and REST API. As a startup, learning from users and reacting to their needs is the highest priority. Angular2 and node allows rapid development of new features with modern designs. Play, a scala web framework, provides our stable REST API for customers that want automated integration.
Amazon Web Services – Managing the sensitivity of healthcare data and would be a daunting task without existing vetted systems. We are able to leverage many services throughout to enable security and compliance — Cloudformation for reproducibility and configuration management, ACM for TLS, custom encryption with KMS, CloudWatch for logging and montoring, very granular IAM permissions, and so on.
ECS, Docker containers, and CircleCI – Continuous deployment at the onset was important to both the engineering team and the business operations. As Amazon’s ECS has matured the ease of managing docker containers across different environments (dev to prod) and growing with our scaling needs has been worth it. CircleCI’s allows us to integrate seamlessly with building git branches and running all of our unit tests, integration tests, and system tests.
Tech Stack Highlights
Flask – we migrated to Flask from Django to increase the flexibility with which we build and manage our portfolio of workflow applications. We manage our own library of plugins and cookiecutters to enable efficient setup for new team members and team members picking up new projects.
React – we moved to React from Ractive as our JS framework for its performance, component oriented architecture, and server side rendering. React raises the level of abstraction in our front-end code base, making it more predictable and allowing our engineers to focus on building functionality versus wrestling with the framework.
AWS – as a healthcare IT company, we need to maintain a very high bar for our security and privacy infrastructure, given the high-stakes nature and stringent requirements of our large hospital system customer base. Our users rely on our ProviderMatch platform to match millions of patients to the right providers every year. AWS is our core cloud platform that allows us to accomplish this at scale.
ElasticSearch – our core patient-provider matching engine is enable by multi-faceted search. We have customized ES to our domain-specific data models, query types, and end user stories. ES recently migrated away from search as a core area of innovation (in lieu of analytics), so while we are investing in ways to optimize our utilization of ES, we also continue to keep an eye on the landscape of alternatives!
Slack – Slack is core to how our team communicates and gains critical insight into how our platform is performing. The ProviderMatch platform’s services are tightly integrated into Slack, and provide notifications and real-time performance insights that allow our team to stay on top of all platform activity.