addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupsimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1outlookpersonJoin Group on CardStartprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Breaking The Monolith: Using Node.js to Rewrite Groupon's Front-End

Make sure to let us know if you need building access! Answer the "RSVP Question" with your full name.

Geekfest is always looking for speakers! Email us at [masked] if you are interested in giving a talk.


Breaking The Monolith: Using Node.js to Rewrite Groupon's Front-End by Sean McCullough

Groupon's monolithic Ruby on Rails application had some major usability and scalability issues. We will discuss how we planned on breaking the monolith apart, how we chose Node.js to replace Ruby for servicing our web traffic, and how we made a major rewrite as painless as possible

Join or login to comment.

  • Sean M.

    June 8, 2014

  • Josh H.

    My mom taught me there was no such thing as a free lunch. She was wrong.

    If you had to go back and do this again, what would you do differently?

    November 6, 2013

    • Josh H.

      Thanks for the thoughtful response

      November 9, 2013

  • Stephen B.

    Interesting talk. I really liked the high level overview but I'd also be interested in some low level Node.js talks as well. Maybe an idea for future talks?

    1 · November 6, 2013

  • George N.

    The speaker seemed knowledgeable about the subject material, but I was disappointed by how little time he spent talking about Node.js. It was more about architectural challenges in rewriting a webapp than focusing on Node.js to rewrite the app.

    November 5, 2013

    • George N.

      That came out a bit harsher than I intended, sorry about that. I did enjoy the presentation a lot. I wish I had asked a question at the presentation, but hopefully you can answer it here.

      What were some of the most useful Node.js features that made the Groupon team decide to use it over something else like a frontend Javascript framework and a RESTful backend in another language?

      You mentioned the layout service which seems very useful. Did Node.js have some functionality that made its implementation very easy?

      November 5, 2013

  • A former member
    A former member

    Very well done, Sean. It was fascinating to see how the Groupon team evaluated several platforms before choosing Node.js for this solution. Even better, the presenter shared how the Groupon engineers dealt with challenges beyond the Node decision, including getting a new engineer's dev environment setup quickly, making decisions on CDNs, keeping the test suite speedy, and increasing the team's truck number through good documentation. Most startups would kill to have Groupon's problems. Sean showed how the team morphed the code base beyond growing pains into today's robust, fault-tolerant app.

    1 · November 5, 2013

  • Paul S.

    Solid presentation - Interesting to see the approach Groupon took to overcome their growing pains. Goes to show, you just never know what to expect when you step outside the box and your comfort zone.

    November 5, 2013

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy