Here you will find ideas and code straight from the Software Development Team at SportsEngine. Our focus is on building great software products for the world of youth and amateur sports. We are fortunate to be able to combine our love of sports with our passion for writing code.
The SportsEngine application originated in 2006 as a single Ruby on Rails 1.2 application. Today the SportsEngine Platform is composed of more than 20 applications built on Rails and Node.js, forming a service oriented architecture that is poised to scale for the future.
Migrating users from one platform to another while still allowing those people to use the platform's applications was no small task. Here's how we did it with no downtime.
Data is useful; there’s no denying that. However, if there’s no way to measure it, is the data still valuable? Hubstats gives Sport Ngin’s Development team an easy way to measure, view, and record GitHub data.
This guide aims to reduce some of the confusion around implementing Elasticsearch indexing within a rails project.
A talk by Doug Rohde. Concepts from the world of design and how they can inform decisions we make as software developers to reduce complexity and increase maintainability.
You should consider the minor consequences of using shell commands with git to list the files of your project in Ruby gemspecs. Considering these small details is important when trying to architect something well.
We are seeing a 33% application response time improvement and the ability to serve twice as much traffic when comparing a new generation c3.2xlarge AWS server directly to the c1.xlarge on real production traffic.
def foo; "foo"; end foo = "bar" if foo.nil? foo # => nil
In the past, we've used fitter_happier for this purpose. Then, we added MongoDB to one of our applications. To check the connection to that database, we had to monkey-patch fitter_happier, which didn't sit well with us. We also wanted to check that our Resque queues weren't backed up, which necessitated further monkey-patching.
I think that we can all agree that Active Record is pretty great. Working with ActiveRecord objects, though, comes at a cost. It has to fetch data from the database and then work with it a bit to give you the easy-to-use object with lots of bells and whistles.