Startups Using CoffeeScript in Boston
Via their job posts and information submitted by startups themselves, these are the Boston CoffeeScript startups we've found.
Interested in other technologies? Browse or search all of the built-in-boston tech stacks we've curated.
Tech Stack Highlights
Ruby / Rails – We use Ruby and Rails for our web facing applications, as well as the API underlying the platform. The entire platform is deployed to Amazon AWS. We haven’t made the jump to Rails 5 yet for existing applications, but it’s on the radar.
AWS – The entire drizly platform is built on AWS. We use a variety of different services, including SNS, Redshift and Lambda, which are used heavily in our data pipeline.
React – Where possible new frontend development is done in React. We have some SPA style projects built in React, as well as a significant number of components on our e-commerce site utilizing react.
Mysql/Postgres/Redshift – Depending on the application we use a slightly different data-store. We like to be flexible, and find the right solution for the problem at hand.
SQS – We utilize SQS heavily as a background job processing system. We’ve found it to be stable, and durable, and performant enough for our use cases.
“DataOps” platform, allowing analytics teams to create processes for working with company data and automate delivery to stakeholders.
Carbon fiber / multimaterial 3D printer. Allowing printing of higher-strength parts.
Text-mining solutions for business intelligence.
Improved visual reporting / intelligence for business data from Salesforce, QuickBooks, etc.
Tech Stack Highlights
Ruby on Rails – We use Rails for most of our services. It’s easy to read, easy to test, reasonably fast to learn, and opinionated in ways that we find helpful.
Elixir – We’re using Elixir for select services where high concurrency is important.
React – We are using React on new frontend features because it’s stateless paradigm makes for code that is easier to reason about and winds up with fewer bugs. It’s also nice to have a single framework across our services, so folks don’t have to learn an entirely new system every time they work on something different.
MariaDB – It seems like everyone is moving to NoSQL data stores, but we love SQL! It turns out that databases that have been around for several decades are very good at what they do — indexing, locking, transacting — and using this proven technology means we get a lot of DBMS features “for free” that NoSQL variants force you to build yourself. We do have a service at scale beyond what a single SQL database can support, and in that instance we are sharded across several database instances.
Docker – All new application servers that we build are containerized and thus entirely immutable. This eliminates an entire class of problems that arise when servers are otherwise left in an unexpected state. We never have to worry about rogue processes, old open ports, or artifacts on the file system impacting a newly-deployed set of code.
Mobile apps for college alumni communities.
Tech Stack Highlights
Ruby on Rails – We’re a Ruby on Rails application running on Heroku with PostgreSQL as our primary database and Redis available for ephemeral data. We use the Fastly CDN for our assets and Cloudinary for file management, in particular, image management. For search, we leverage Postgres’s full-text search with the pg_search gem.
Segment and Redshift – We use Segment to collect analytics about the usage of our app. We use their analytics-ruby gem and analytics.js library for back-end and front-end analytics respectively. We then leverage them to pipe the data into an Amazon Redshift data warehouse where we can analyze the data. Recently implemented Chartio to visualize that data with dashboards.
Front End Technologies – We use SASS for CSS management, Haml for HTML, and coffeescript to more cleanly write javascript. We also use Modernizr for gracefully degrading CSS features. We use Foundation Framework to make our application responsive.
CircleCI – We use continuous deployment as our deployment strategy. Every pull request is code reviewed in GitHub and deployed to an integration environment where it’s available for the reviewer, the developer, and anyone else in the organization to test and review. Additionally, we have a suite of thousands of unit tests built on MiniTest and feature tests built on Capybara, running continuously on every commit with CircleCI. Assuming it passes all our checks, manual and automated, it’s then merged into master and deployed to production by Heroku.