Geekon: I-Tier

23 Responses to Geekon: I-Tier

  1. Ferdian
    October 8, 2013 @2:11 am

    Nice!!!!
    its good Choice, nodejs is very rocks now, it’s future of web architecture!!!

  2. Drew
    October 8, 2013 @5:36 am

    Bro, WEBrick isn’t very good in production. It’s just not webscale. Let me know if you need help deploying with something else.

  3. October 8, 2013 @11:27 am

    We’re holding an event in Philly (Hack and Hops) in November featuring talks about node projects and why to use node.js over other languages. Any thoughts about Groupon’s possible participation in speaking and in particular about this switch?

  4. Dehru
    October 8, 2013 @3:31 pm

    Great to see node working so well for you.

  5. Jorge
    October 8, 2013 @4:02 pm

    Do you still using Rails in backend SOA services o replaced it completly with Node.js services?

    Some graphics or your architecture might be cool :)

    • Sean McCullough
      October 9, 2013 @12:48 pm

      We’ll be following up with lots more information over the next month or so. Can’t wait to share it with everybody!

  6. Kevin Krauss
    October 8, 2013 @4:30 pm

    Nice dood! I <3 node and I am happy to see this great report. I do also love ruby though and I think that it can be scaled.

  7. October 8, 2013 @6:15 pm

    Does anyone else find this fascinating that Ruby on Rails was compared to an SOA architecture? Are those really apples to apples?

    • Sean McCullough
      October 9, 2013 @12:50 pm

      Sorry, i didn’t mean it that way.

      We had an architecture problem primarily: Our Ruby on Rails app became a difficult to manage monolith. We use Ruby on Rails for many of our backend services. More to come soon.

  8. Lee
    October 8, 2013 @9:06 pm

    a good choice. node.js is cool

  9. October 8, 2013 @11:51 pm

    good news, it’s about time to say goodbye to RoR

  10. October 9, 2013 @12:35 pm

    This is awesome! Would love to read about how the transition went. Node FTW!

  11. October 10, 2013 @8:48 am

    “…and we will be blogging stories about this intense transition.”

    ~refresh~

    ~refresh~

    ~refresh~

  12. October 10, 2013 @9:52 am

    Great news!

  13. nakupanda
    October 10, 2013 @7:43 pm

    Hi,

    next time when you are starting a new website will you still use RoR as your first choice?

    thank you.

  14. October 10, 2013 @8:07 pm

    So you had an app that lacked structure, and now it seems like you have an app with a better structure. The fact that these 2 use different languages is wrongfully highlighted in this post.

    • Gavin
      October 13, 2013 @1:16 pm

      I’m also confused by Sean’s post. Everything that was lacking with Groupon’s site could have been solved by using distributed Ruby server apps, and didn’t require a complete rewrite. There must be other issues that led to this decision, which I happen to be very interested in reading about. I am a fan of node.js and I’m trying to figure out how it makes companies more money.

      • Sean McCullough
        October 13, 2013 @1:28 pm

        We could have easily used Ruby to solve this problem, but we went with Node after some consideration. Keep your eyes peeled for a followup post with more details about why we chose Node.js.

  15. October 11, 2013 @11:35 pm

    Can you post some numbers about your transition? How many servers cuts, which packages did you choose? A little about your stack and architecture? That would be great

    • Sean McCullough
      October 13, 2013 @1:26 pm

      We’re working on follow up posts with this kind of detail soon.

  16. October 16, 2013 @10:09 am

    We (asw.com) moved to the same web-app-as-API-client approach earlier this year, and are slowly transitioning away from monolithic Rails backend to a collection of services. Its definitely the way to go, I think. The ‘single contract’ thing is really great – felt good when all we had to do to add a new section to our mobile app was deliver the API docs for the endpoints to our mobile app developers and sit back :)

    I think another benefit of SOA is the ‘horses for courses’ thing, whereby you can pick the best technology stack for each service – we have a Geo service built on top of PostGIS, and a messaging system built on MongoDB.

    Interesting times ahead :)

  17. October 18, 2013 @2:16 am

    Hey man you always says follow up post where is follow up post about this transition. Eagerly waiting…………….

  18. October 30, 2013 @11:06 pm

    The first followup post is now live at: https://engineering.groupon.com/2013/misc/i-tier-dismantling-the-monoliths/

    Great work!

Leave a Reply

Your email address will not be published. Please enter your name, email, and a comment.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Scroll to top